A discussion from the security community prompted a question that is to do with SMF:
* can a service be described in such a way that it only starts if there is another service that depends on it to be enabled? The service here in question is svc:/network/rpc/bind. Ideally that service should never need to run *unless* there is something that uses SunRPC. So upon booting, the service would be "offline" and there would be no explicit node in the SMF dependency tree that pointed to it being enabled. Only when SMF went to start something like svc:/network/rpc/keyserv, it would look at the list of things that this wanted, notice that svc:/network/rpc/bind was not online and bring that online. I suppose that kind of implicit knowledge being placed in services and not easily visible could be a dangerous thing and make it harder to diagnose faults (among other things.) Are there other caveats I'm missing here? Darren
