> > The main one is the "Hangup caught" which is a likely refresh of the SMF > service, and it seems that punchin does this in the nwam_nss function in > cleanup.solaris.kshlib, which does a refresh of nwam, to get the update to the > SMF property: > > nwamd/use_net_svc > > which isn't present for NWAM Phase 1... > > The attached patch to punchin fixes this by first checking that the property > exists, if not, then don't try set it or refresh nwam.
This parameter was added in NWAM phase 0 specifically for tools like punchin and netprof and other things that want control of things like resolv.conf, default routes, etc. to tell NWAM to "lay off until I tell you otherwise". I've integrated your change, but if we don't implement the new network profiles, will NWAM go merrily reconfiguring the network every time it gets a DHCP update? Or will this just work persistently? Note I am not opposed to changing the network setup to use a profile if that's what is required but want to make you aware of the original issues we saw. Thanks, -Paul
