Renee Danson wrote: > Thanks Alan, Anurag, and Darren for the doc review. I've updated > most all of the spec pages, as well as the 20qs doc that's linked > to from the nwam wiki page. > > Anurag's comments raised two small questions: > > >> Renee Danson wrote: >> >>> I've made the following doc updates, in preparation for our PSARC >>> commitment review: >>> >>> * Completed the (hopefully!) final update of the Phase 1 Spec, found at >>> http://opensolaris.org/os/project/nwam/p1spec >>> >>> >> Section 3.1 >> >> - "default-domain" property: system/identity:domain is not >> refreshed/enabled. It reads from /etc/defaultdomain to set the >> domainname(1M). >> > > Hmm. I see why we wouldn't want to restart the service and have it > re-read from /etc/defaultdomain; but the refresh is also useful in > terms of allowing the change to ripple throughout the system. For > example, I know smtp:sendmail has a 'restart_on refresh' dependency > on identity:domain; I suspect it's a service that would like to > know if the domain has changed. > > We might need to create a refresh method for identity:domain that > basically acts as a trigger for those notifications (a :true > refresh/exec property is probably about all we need); but then, > we'll also need to test what happens when we do that--how different > services respond to the (until now only theoretical) refresh of > identity:domain. > That's right. identity:domain will have a "restart_on refresh" dependency on network/location. Thus, when network/location is refreshed, identity:domain will be refreshed too.
Because identity:domain reads from /etc/defaultdomain (rather than domainname(1M)), installing a location will involve writing the default-domain to both /etc/defaultdomain and domainname. I'll work these changes into the network/location manifest and script. > >> Question 11: >> >> - doors are created in /etc/svc/volatile and /etc/svc/volatile/nwam >> > > Seems like we should just use one directory; I would be inclined to > consolidate into /etc/svc/volatile/nwam. Any reason why we shouldn't > do that? > The /etc/svc/volatile/nwam directory is created by nwamd start script. The backend door will be created by netcfgd before nwamd starts. I don't see why netcfgd cannot create the nwam directory. Alan should have a reason. (I'll also move the legacy location creating script to inside the nwam directory in /etc/svc/volatile.) Anurag
