On Thu, 2007-09-13 at 19:19 -0400, Jon Nettleton wrote:
Sure now you start answering the hard questions. Well the scripts I
use are all based around the same generic dispatcher.d script. The
only variance is whether you check in /var/lock/subsys or /var/run to
figure out if the daemon is always running. Other than that they just
run service NAMEOFSERVICE on/off/restart. If we could standardize and
put all our lock files or pid files in a single place then we could
run a single script from dispatcher.d that wraps symlinks put in
/etc/rc.d/rcN.d/ and does the appropriate thing to the service.
hmmm, that is confusing.
on interface up it loops through
/etc/rc.d/rcN.d/S(*) and either service $1 start or service $1
restart depending whether
/var/run/$1 exists or not.
Now that I look at it like that does it make sense to make
network-services an actual init-script that is responsible for for
If we are running NetworkManager it is activated through dispatcher.d,
otherwise we just enable it in standard init after network.
I think that should work.
So I talked a bit to Dan Williams about this today, and he said that
the dispatcher will need a bit of love for NM 0.7 to handle the fact
that there will possibly be multiple active interfaces, and one default
interface. Services could adapt to changes in the set of available
interfaces in smarter ways than just ifup -> service start, ifdown ->
Correct me if I am misremembering, Dan.