On Thu, 2005-02-03 at 11:08 +0100, Harald Hoyer wrote: > Jeff Pitman wrote: > > On Thursday 03 February 2005 02:50, John Thacker wrote: > > > >>On Thu, Feb 03, 2005 at 02:02:24AM +0800, Jeff Pitman wrote: > >> > >>>Crazy idea: shut off all the daemons that need network (from normal > >>>init processing) and then only spawn them when appropriate from > >>>NetworkManager. > >> > >>Definitely crazy until NetworkManager can actually handle all > >>connections. For example, right now it can't handle any machine with > >>multiple active connections, which includes machines that do > >>connection sharing. (Among other things, it doesn't believe that you > >>would have a static IP with no default gateway.) > > > > > > And, it needs to handle virtuals: OpenVPN, VmWare, vpnc, etc. etc. > > > > Definetly a job for DBUS messaging... How about a general stub for > (re-)starting all kinds of daemons, which listens on DBUS for a specific > signal/message? NetworkManager and /etc/init.d/network could provide this > message, after the network is up. Seth's thoughts on SystemServices are good: http://www.gnome.org/~seth/blog/2003/Sep/27 The Python part is irrelevant here; what's important is the idea of a "services manager" process which knows about service dependencies and when to restart them. So in this situation, NetworkManager wouldn't tell ntpd to start directly; instead, NetworkManager would tell ServiceManager that the "org.freedesktop.NetworkManager.Link" dependency was available. ServiceManager would then recheck its list of pending activations and start all services that were now runnable with this dependency. Likewise, when a dependency goes away, ServiceManager stops all services with that dependency. So dependencies can either be other services or they can be sub-components of a service, like "Link".
