On Fri, Nov 16, 2007 at 04:03:47PM -0800, Darren Reed wrote: > ... > Windows allows enable/disable of services to be managed seperately > from start/stop (although you can't start something that is disabled > and has no backdoor access.) Solaris has placed svcadm in front > ...
Exactly. The Windows distinction between start/stop and manual/ automatic is intuitive and handy, and it's what _I_ find missing in SMF. At a glance I want to know: a) will this service start at next boot, b) is it running now. And I want to be able to change those two things independently. SMF could make more or less that same distinction. We can argue about synch vs. async, recursive vs. not, but IMO those are all incidental issues -- the key thing is the distinction between running/not running vs. will/won't start at next boot. Nico --
