Quoth Dave Miner on Thu, Sep 21, 2006 at 10:06:57AM -0400: > >Below is the table of services that have dependencies on these obsoleted > >services: > > > >service name state in standalone profile > >------------------------------------------------------------------- > ... > >network/inetd:default disable > > I see no reason why inetd should be disabled by default in a standalone > or any other profile that Solaris provides by default; its only function > is as a listener/restarter for other services, each of which can be > enabled/disabled directly.
Isn't it a waste of resources if, in the vast majority of cases, nothing will connect to it? > The only thing that disabling it will do is > make the first inetd-restarted service which is needed not run until the > administrator also enables inetd, which is clearly an undesirable two-step. Hmm, that would be undesirable. I think it's a generic delegated restarter-related problem, though. I suspect it would be better to introduce svcadm enable -i (interactive) which said "I've enabled your service, but it can't start because its restarter is disabled", and make sure that svcadm enable -r enables the restarter. David
