Christine Tran writes: > Hi, > > Yes, that should work, but the point is moot since if you have your > zones:default in the permanent online state (not using a -t), your > general/enabled property should have been, and probably was a "true". > So setting it to "true" again does nothing. If you use svcprop to > examine the property again, did it report "false"? > > Mine said "false", and I wonder where it got the "false" from.
You haven't refreshed the service, so the 'false' is what's in the running copy. Sadly, general/enabled is 'special', and we need to look at the most current value so that we didn't have to require that every update to enabled required a refresh of all properties. The implementation is subtle and makes behaviour like this hard to understand, so needs to be fixed. Here's one bug that describes the problem: 6234283 svcprop isn't always accurate for queries on general/enabled We're kicking around ways to resolve the general/enabled behaviour as part of Enhanced Profiles. Expect muttering about snapshot and other model improvement in future versions of that project's documents. We'll appreciate feedback once we have a reasonable and coherent proposal. In the meantime, svcadm and svcs recognize the implementation subtleties and handle them for you. (The problem is that the model has tons of flexibility and support for future features, but is hard to understand at the basic level. We'd like to retain the flexibility in the design while simplifying interactions with the model.) liane -- Liane Praza, Solaris Kernel Development liane.praza at sun.com - http://blogs.sun.com/lianep
