I was helping a user with a service property issue w/rt the Secure by Default project where in order for the user to get mail, sendmail needed to have its: 1) config/local_only property set from true to false 2) service refreshed 3) service restarted
The user was booted into his older (build 29) environment, so we used svccfg's "repository" command to switch to the newer (build 49) repository, the "listprop" command to verify that the property was still true, then the "setprop" command to set it to false. Then we made the mistake of assuming that a reboot back to the build 49 environment would constitute an automatic refresh and restart of the service. But it didn't. Fortunately, an SMF expert happened to walk by just at this time, and told us that we needed to refresh the service even after rebooting; once we did so, `svcprop` started reporting the desired value, and a subsequent restart of the service resulted in mail flowing. So my question is: why didn't the reboot constitute an automatic refresh as we thought it would? The current behavior seems counter-intuitive. -- John http://blogs.sun.com/jbeck
