Rainer Heilke wrote:

>Mark Martin wrote:
>  
>
>>[cc'ing sysadmin-discuss]
>>
>>[context setting -- my original email proposal that started the thread 
>>on smf-discuss. my reply follows]
>>Gang,
>>
>>I believe there's minimal consensus that start/stop as an alias for 
>>enable -t does have some value, if only for historical connotations.  
>>After re-reading the discussions here many times, I believe here's how 
>>I'd like to proceed.  I'm going to assume that this is the correct 
>>approach unless someone tells me I will get veto'ed at RTI time.
>>
>>(continuing the list thinking meme)
>>I will create a new svcadm start command which will an alias for enable -st
>>I will create a new svcadm stop command which will be an alias for 
>>disable -st
>>start -r will be available, but not the default
>>start will report non-started (or enabled) dependent services that 
>>prevent it from continuing (unless the -r option is specified).
>>    
>>
>
>Please see my other emails (including the one sent just before this 
>email). I (personally) see "start" merely being an alias to "enable -st" 
>to be of little or no value. It buys us nothing. :-(
>  
>

To add to Rainer's point, something that I see missing from
"enable -st" is the ability to start without all of the dependencies
already being "online".

To pick out a service, I'm going to choose inetd.  Its dependencies
are listed as:
# svcs -d network/inetd
disabled       May_24   svc:/network/inetd-upgrade:default
online         May_24   svc:/network/loopback:default
online         May_24   svc:/milestone/network:default
online         May_24   svc:/system/filesystem/local:default
online         May_24   svc:/network/rpc/bind:default
online         May_24   svc:/milestone/name-services:default
online         May_24   svc:/milestone/sysconfig:default

...this implies that inetd won't start if NIS hasn't started (nis/client
is required for name-services.)  This prevents me from starting
up and allowing ftp/telnet - not so useful - to accounts that are
present in /etc/passwd.

So, if my box boots, runs into issues and can't initialise itself
as a NIC client (when so configured), other things fail and cannot
be started when it is likely that I would find it useful for them to
be active/available, even if they're in a degraded mode of service.
Now because SMF isn't going to allow me to start inetd (due to
nis/client being absent), I'm forced to either start inetd manually
or run the start method for network/inetd myself.

Darren


Reply via email to