Liane Praza wrote: > Sebastien Roy wrote: [snip] > > (It would be nice if svc.startd were a bit more specific in that log > > message, but that's not the core issue.) It proceeds to stop and start > > network/physical:nwam. Why does it do this? Is nwamd not to be trusted > > to notice that it's unable to acquire a DHCP lease on this interface and > > deal with this on its own? nwamd is likely capable of noticing that > > something went wrong with the network interface it was responsible for > > and to either retry to acquire a lease, or try on another network > > interface. Even if it's not, it's not inconceivable that it could be. > > nwam would need to tell startd that it manages its child processes. It > can do that by launching subprocesses in their own contracts.
Erm... does that apply to all services ? For example... what will happen if I create my own service using a shell which creates worker chilren on demand which are reaped from time-to-time (and not immediately) ? ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.mainz at nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;)
