I have the following set of init stuff:
net.wireless depends on ipw3945d
ntp-client depends on net
net.wireless automagically starts when the interface "wireless" appears
net.wireless is in the boot runlevel
When I boot the computer, it starts ipw3945d before net.wireless, but not
in time for the "wireless" interface to appear before it tries to start
net.wireless. Moments later, the interface appears, and it runs
net.wireless again, asynchronously, and it spends a while starting up (it
has to find the correct network, and dhcp, etc).
While net.wireless is starting up, the system synchronously starts
ntp-client, which attempts to start net.wireless; this fails (it's already
starting), and so ntp-client fails. Then the asynchronous net.wireless
finishes starting, and I have network, but no ntp-client.
Is there some way to teach start-stop-daemon that, if a dependancy fails
because it is already starting up, this means you should wait for it, not
give up? The other stuff is a bit odd, but ultimately harmless, aside from
the fact that stuff gets confused by this situation.
-Daniel
*This .sig left intentionally blank*
--
[email protected] mailing list
