On Tue, 2008-04-29 at 16:43 -0700, David Powell wrote: > Sebastien Roy wrote: > > 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. > > SMF will trust nwamd to handle failures of the commands it runs, but > nwamd needs to communicate that it deserves that trust. There are > two ways of doing that: > > a) "I'm moving out" > > Use startd/ignore_error to tell svc.startd to ignore processes > that dump core. Note that this will also ignore nwamd when it > dumps core. > > b) Take responsibility > > If a subcomponent may fail and you don't want its failures to be > conflated with nwamd's, start it in a separate contract.
b) seems like a more sensible option. I'll file a bug against nwamd. Thanks! -Seb
