>(b) Temporary should *not* be the default. This one I believe we got right. > A very common admin mistake is to go turn something on, assume all is > well, and then oops, 3 months later someone reboots the box and you have > this lurking timebomb that the service wasn't permanently enabled.
I'd call that "legacy Unix behaviour"; and people get that wrong all the time considering questions like ``how to make "route add" or "ifconfig"'' stick; SMF is a great step forward and more simple persistent commands are required (we're slowly adding them but, e.g., you can't yet configure your network with permanently using something other than a file editor) >So my opinion is this: > >- keep svcadm enable as is for compatibility >- make svcadm start the same as enable -r -s >- make svcadm start -t mean svcadm enable -r -s -t, > i.e. force the user to express the less-common case of temporary enable >- make svcadm stop the same as disable -s (not recursive, not temporary) +1 Casper
