On Monday 09 of March 2015 19:05:19 Patrick Shanahan wrote:
* Moby
[03-09-15 19:00]: Thanks auxsvr, that worked. Is there an indication in the logs etc that one can check for and accordingly restart systemd-logind? or should I just have it restart with some frequency via cron?
istm that this pblm appears whenever ssh, system networking or system security files are updated that it happens. Which ever app is causing the pblm should restart/reload the service itself, but doesn't :^(.
If I remember correctly, it is only necessary after some updates of systemd, glibc or dbus, i.e. updates that affect systemd and/or dbus, but such updates do not necessarily update already opened files of systemd-logind, which implies that zypper ps will not indicate the need to restart the service. I don't know much about systemd to explain in more detail. -- Regards, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org