[sles-beta] SLES12 RC2 x86_64 Login possible even though autoyast init-script is still runing

[urs.frey at post.ch]

Hello Mark

>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.  :(
Thank you very much for your answer, brining me a bit closer to systemD

Question:
Is there a way to list this system class of static services

I googled a bit, but nil found. Manned also (man -k systemD | systemctl), but nil found
Also in the sles_admin_book_en.pdf there is nothing to find

I would like to learn more about those "static classes" in systemD

Thank you very much
Best regards

Urs Frey                                              
Post CH AG
Informationstechnologie
IT Betrieb 
Webergutstrasse 12 
3030 Bern (Zollikofen) 
Telefon : ++41 (0)58 338 58 70 
FAX     : ++41 (0)58 667 30 07 
E-Mail:   urs.frey at post.ch

-----Ursprüngliche Nachricht-----
Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Mark Post
Gesendet: Friday, September 05, 2014 6:57 PM
An: sles-beta at lists.suse.com
Betreff: Re: [sles-beta] SLES12 RC2 x86_64 Login possible even though autoyast init-script is still runing

>>> 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

_______________________________________________
sles-beta mailing list
sles-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/sles-beta