On Mar 15, 2012, at 12:25 PM, Dave Miner wrote: > On 03/14/12 22:33, Jesse Butler wrote: > ... >> Proposed solution >> >> The actions which will cause a local DHCP configuration to be >> automatically updated are 'create-service', 'delete-service', >> 'create-client' and 'delete-client'. Rather than add a new switch to >> each of these commands, I'd prefer to add a single boolean SMF >> property to the AI service, 'manage-dhcp' or similar. The '-i' and >> '-c' options will behave as they are currently do for >> 'create-service', but will issue a warning if 'manage-dhcp' is not >> set to true. For all implicit automated configuration changes, if the >> property is true, we will behave as we currently do. If set to false, >> then we'll not attempt to update the configuration at all. >> >> I believe that this value should default to false, so that default >> behavior out of the box is to not alter any configuration unless >> requested to do so. >> > > Is there evidence to support that the majority of the cases where DHCP > configurations might be manipulated are ones that installadm should not be > updating? We generally make defaults conform to the expected common case. > > Dave
Good question, but I simply don't have data. I sort of made a guess to begin with, as I described, and it seems like I chose the wrong path. Given that configuration updates are destructive, in the absence of solid data I'd prefer to opt for turning it off by default. _______________________________________________ caiman-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
