Dan Williams wrote:
On Tue, 2008-12-16 at 17:47 -0500, Jeremy Katz wrote:
On Tue, 2008-12-16 at 16:30 -0600, Chris Adams wrote:
Once upon a time, Jesse Keating jkeating@redhat.com said:
On Tue, 2008-12-16 at 16:41 -0500, Seth Vidal wrote:
so a good reason to power off is simply to save power
Or to reboot for one of our frequent updates that require it. kernel, dbus, etc...
Why does anything other than a kernel update require a reboot?
The system bus cannot be restarted. Similarly, any apps you have running will be using old libraries so things like glibc you really want to reboot for.
The problem is mainly one of state. For example, NetworkManager has some code to handle reconnection to the system bus. But to transparently handle bus restarts, NetworkManager would have to perform the following actions; none of this is NM or D-Bus specific, it would be the same problem in any system using separate services for specific functions, as is the unix way.
*snip*
We've discussed less-invasive ways of fixing this, like queuing signals in the services on the service-side in libdbus or so until the service reconnects to the system bus, but that could be quite tricky and error prone. You cannot do a 75% solution here.
Dan
Of course all this is SEP when dbus becomes a kernel module :)
--CJD