On 03/10/2015 03:39 AM, auxsvr@gmail.com wrote:
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.
It is possible that an update affects a config file. Hmm. If the config file is open, read, then closed, it won't show up in any kind of dependency trace, even if 'zypper ps' does more than just look at running executables. If it ONLY looks at running executables then of course a config file change won't be in its purview. However if the executables that use the config file do the open-read-close then a change to the config won't affect them. Neither will a change affect them if they hold open the original config file since that's the way Linux files work. I have not observed this problem, but that may simply be because of the timing of updates vs my use of ssh. However if it did occur on my system I would make use of the snapper updates to do a 'diff' since my rootFS is on BtrFS. That strikes me as easier than pouring though other listings to seek out the delta concerned. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org