* Frederic Crozat <fcrozat@suse.com> [04-05-16 12:38]:
Le mardi 05 avril 2016 à 12:31 -0400, Patrick Shanahan a écrit :
* Frederic Crozat <fcrozat@suse.com> [04-05-16 11:45]:
Le mardi 05 avril 2016 à 12:34 -0300, Cristian Rodríguez a écrit :
On Tue, Apr 5, 2016 at 11:35 AM, Patrick Shanahan < paka@opensuse.org> wrote:
* Ludwig Nussel <ludwig.nussel@suse.de> [04-05-16 06:41]:
Please note that this mail was generated by a script.
Again debus-daemon is replaced and must be restarted resulting in dropped internet connection (wicked). And remote administration requires a minimum of rebooting subject machine or physical access :(
That's not how it works.. dbus needs to be restarted only when it gets updated and not when a third party component is.
And even in that case, dbus should never be restarted, most applications don't support it (which is why dbus package doesn't restart system bus..).
then what is one to do with:
~ # zypper ps -ss The following running processes use deleted files:
PID | PPID | UID | User | Command | Service -----+------+-----+------------+-------------+------------- 1084 | 1 | 499 | messagebus | dbus-daemon | dbus
I understand this to indicate: systemctl restart dbus
is one to just ignore this?
YES !
Never restart dbus.. If you see stuff failing apart after restarting dbus, this is "expected"..
I would guess then that this is widely known in more regular circles than just dev's??? because I have not ever noticed any conversation here about that. Maybe zypper should ignore that or advise not to restart or .... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org