Francesco Poli wrote: > On Sat, 09 May 2009 00:49:31 +0200 Michael Biebl wrote: > >> Francesco Poli (t1000) wrote: > [...] >>> As a consequence, I cannot understand what's the correct strategy >>> to restart the daemon, when I need to (e.g.: because checkrestart >>> suggests to do so, after a package upgrade). > [...] >> console-kit-daemon is a D-Bus activated system service. >> If you want to restart it, simply kill the process and D-Bus will launch it >> on >> demand. There is no need for a legacy sysv init script. >> >> It's not recommended to restart console-kit-daemon anyway, as you will lose >> all >> registered sessions. > > Well, but what if a security update on one of the dependencies creates > the *need* to restart the daemon? > This is the first time I encounter a daemon which I should try to never > restart... :-o
iirc udev is also not restarted on upgrades, so is /sbin/init, or wpasupplicant. The easiest way is to simply restart the system. > It sounds kinda strange that I am recommended against restarting a > daemon! > >> Hope that answers your questions. > > It does answer my questions, but it also generates even more > head-scratching! :-/ Well, you can restart consolekit, but then you will have unexpected behaviour (users in the desktop session will no longer be able to suspend/hibernate/shutdown etc). Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
