>As more of an admin than a developer, I agree the centralized >enable/disable of SMF is valuable. As are the log files you mention >below. Some configurability in SMF is also useful, starting multiple >instances of the same service for instance.
Personally, I think we already erred too much on the side of put it in SMF for some of the older services and newer services. The Registry model is NOT one to aspire to. For one I strongly dislike the fact that I never have an idea what is the current property and which would be the property value on boot; clearly they are different at times. Secondly, SMF has already proven to me to be too fragile because either the underlying database technology is not reliable or the way it uses that technology is prone to failures. Powercycling a system during certain parts of boot is almost guaranteed to cause the next boot to fail with a corrupted registry. The fact that that is even possible concerns me greatly; recovery is easy but requires manual intervention. (I'm an engineer, not a politician so I don't feel compelled to first state the things I like about SMF) Casper
