First up, I'm not a DBus daemon developer.
I disagree that the DBus daemon should never be restarted because the
NetworkManager developers say so. This is a step towards the "dark
side" - rebooting your box after performing an upgrade is the M$ way of
doing things. Solid engineering can prevent this.
I have no idea if the following is possible, but it may be a good start
to solving the DBus upgrade/restart puzzle:
1. Start new DBus daemon on a new socket:
/var/run/dbus/system_bus_socket.new
2. Connect to the old socket and start proxying messages between the 2
daemons.
3. Move the new socket over the top of the old socket:
mv /var/run/dbus/system_bus_socket.new /var/run/dbus/system_bus_socket
4. Send message to the old daemon to force disconnection of all clients
which should reconnect to the new daemon, once all clients disconnected
then the old daemon shuts down.
Comments?
--
Regards
Tyson Clugg
Programmer
=============================================================
Unique Micro Design Pty Ltd.........engineering ICT solutions
Wellington Road Business Park
200 Wellington Road
Clayton, VIC 3168, Australia
PO Box 4297, Mulgrave, VIC 3170, Australia
+61-3-9582-7095 [EMAIL PROTECTED] DIRECT
+61-3-9582-7070 [EMAIL PROTECTED]
+61-3-9582-7060 [EMAIL PROTECTED]
+61-3-9582-7050 [EMAIL PROTECTED]
+61-3-9582-7010 [EMAIL PROTECTED]
+61-3-9582-7000 [EMAIL PROTECTED]
+61-3-9582-7001 Fax - Sales and office
+61-3-9582-7069 Fax - Service
===========================================================
www.umd.com.au UMD Web Address
www.umd.com.au/rfid/ UMD and RFID
www.umd.com.au/gprs UMD and GPRS
www.umd.com.au/solutions/ UMD Solution Sourcing
www.cardgate.net UMD E-Commerce Division
===========================================================
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
