Jordan Brown wrote: > On the other hand, declaring it in the manifest means that it's visible > by default through svcprop and svccfg listprop. Since it's an > undocumented option that users should never have to mess with, that > seems undesirable. > > What I would like would be a way to declare a property to be "hidden", > so that by default it isn't shown by any of the user interfaces. If > it's set to a non-default value, then it should be shown.
Yuck. I think I'd rather see this trait of SMF used to drive a friendlier administrative model rather than used as an excuse to hide things from the user. In other words, it seems to me that SMF's svcprop and svccfg mechanisms are very low-level details that administrators ordinarily shouldn't have to deal with. If the service you are talking about had a customized administrative interface layered on top, rather than relying on SMF's internals as a primary interface, then there likely wouldn't need to be much of a reason to "hide" anything. I do like the idea of being able to say "please show me the variables set to a non-default value." That sounds like a possibly useful "listprop" mechanism, especially for debug. But I don't think it's a substitute for making the service friendly to users. -- James Carlson 42.703N 71.076W <carlsonj at workingcode.com>
