On Fri, 2007-09-14 at 23:11 +0200, Nils Philippsen wrote:
Now what I really don't want to do is deal with service type
transitions
(NMD gets stopped -> network-based services get normal SysVinit services
again) as I don't see real value behind it. If network-based services
need a daemon to run properly then it better ran. It's not really a new
situation -- if xinetd doesn't run, xinetd-based services don't get
started. Just as with every other basic building block of the system.
Makes sense?
As long as it will be able to support both traditional networking setups
(for servers) and NM-based setups, it should be fine. I don't think
going back and forth between these two at runtime is very interesting.