What's the *functional* difference between milestone "multi-user-server" and "all"? I found that these services are disabled in "multi-user-server" where they are online in "all".
disabled 11:40:08 svc:/system/console-login:default disabled 11:40:08 svc:/network/service:default disabled 11:40:08 svc:/application/font/fc-cache:default disabled 11:40:08 svc:/application/print/ipp-listener:default disabled 11:40:08 svc:/application/print/cleanup:default disabled 11:40:08 svc:/application/font/stfsloader:default disabled 11:40:09 svc:/application/print/rfc1179:default disabled 11:40:09 svc:/application/x11/xfs:default disabled 11:40:09 svc:/system/coreadm:default disabled 11:40:09 svc:/system/sac:default disabled 11:40:09 svc:/system/keymap:default disabled 11:40:09 svc:/network/finger:default disabled 11:40:09 svc:/network/ftp:default disabled 11:40:09 svc:/network/login:rlogin disabled 11:40:09 svc:/network/nfs/rquota:default disabled 11:40:09 svc:/network/rpc/rstat:default disabled 11:40:09 svc:/network/rpc/rusers:default disabled 11:40:10 svc:/network/rpc/smserver:default disabled 11:40:10 svc:/network/security/ktkt_warn:default disabled 11:40:10 svc:/network/shell:default disabled 11:40:10 svc:/network/telnet:default disabled 11:40:10 svc:/network/rpc-100235_1/rpc_ticotsord:default disabled 11:40:10 svc:/network/rpc-100083_1/rpc_tcp:default disabled 11:40:10 svc:/network/rpc-100068_2-5/rpc_udp:default One could argue that shell, ftp, telnet etc. should be enabled in a milestone called "multi-user-server", since that's analogous to run-level 3 and the old rc script was rc2.d/S72inetsvc. In fact, why even have a milestone called "all" at all, why couldn't we have started everything up at multi-user-server? --------------------------------------------------------------------- I use svcprop -p options_ovr/milestone system/svc/restarter:default to find my current milestone. If the box has just gone straight from booting to "all", running this command gives me an error message. If I were to bring the box down to another milestone, then back to "all", running this command gives me "all", the correct milestone. Please see below. # svcprop -p options_ovr/milestone system/svc/restarter:default svcprop: Couldn't find property `options_ovr/milestone' for instance `svc:/system/svc/restarter:default'. # svcadm milestone multi-user-server Requesting System Maintenance Mode Root password for system maintenance (control-d to bypass): single-user privilege assigned to /dev/console. Entering System Maintenance Mode # svcprop -p options_ovr/milestone system/svc/restarter:default svc:/milestone/multi-user-server:default # svccfg -s system/svc/restarter:default svc:/system/svc/restarter:default> listprop options_ovr* options_ovr framework NONPERSISTENT options_ovr/milestone astring svc:/milestone/multi-user-server:default # svcadm milestone all # svcprop -p options_ovr/milestone system/svc/restarter:default all # svccfg -s system/svc/restarter:default svc:/system/svc/restarter:default> listprop options_ovr* options_ovr framework NONPERSISTENT options_ovr/milestone astring all Why does options_ovr/milestone not exist when the box first boot up? The only other ovr thing that comes to mind is when I use the -t option to temporarily enable/disable a service, then I have general_ovr/enabled in the instance. --------------------------------------------------------------------- Customer thinks it would be useful for SMF to incorporate a time component. Seeing that services are now controlled using svcadm, he thinks its superfluous to have to atjob some service that he wants to turn on a 10Pm and stop at 2AM, say. I agree with him; also, cron is OK but is there any reason why we can't/shouldn't make SMF handle cron-like service management? CT
