[sles-beta] SLES12 RC2 x86_64 Login possible even though autoyast init-script is still runing
Mark Post
mpost at suse.com
Fri Sep 5 10:56:57 MDT 2014
>>> On 8/27/2014 at 04:38 AM, <urs.frey at post.ch> wrote:
> Aug 27 08:13:59 h05cnh systemd[1]: Started Login Service.
> Aug 27 08:13:59 h05cnh systemd-logind[10059]: New seat seat0.
> Aug 27 08:13:59 h05cnh systemd-logind[10059]: Watching system buttons on
> /dev/input/event2 (Power Button)
> + systemctl disable systemd-logind
> + systemctl stop systemd-logind
> +sleep 300
> + systemctl enable systemd-logind
> The unit files have no [Install] section. They are not meant to be enabled
> using systemctl.
> Possible reasons for having this kind of units are:
> 1) A unit may be statically enabled by being symlinked from another unit's
> .wants/ or .requires/ directory.
> 2) A unit's purpose may be to act as a helper for some other unit which has
> a requirement dependency on it.
> 3) A unit may be started when needed via activation (socket, path, timer,
> D-Bus, udev, scripted systemctl call, ...).
There is a class of service files that are called "static." They cannot be enabled or disabled, per se. It would be nice if systemctl disable would tell you that. :(
You _can_ mask/unmask them, however. So, try this:
systemctl mask systemd-logind.service
systemctl stop systemd-logind.service
systemctl unmask systemd-logind.service
systemctl start systemd-logind.service
Mark Post
More information about the sles-beta
mailing list