Renaud Manus - RPE Approachability wrote: > Darren Reed wrote: > >> Renaud Manus - RPE Approachability wrote: >> >>> Darren Reed wrote: >>> >>>> Renaud Manus - RPE Approachability wrote: >>>> >>>>> You can use svcprop(1) for that: >>>>> >>>>> e.g. >>>>> # svcadm disable -t svc:/system/cron:default >>>>> # svcprop -p general_ovr/enabled svc:/system/cron:default >>>>> 2>/dev/null >>>>> false >>>>> # svcadm enable -t svc:/system/cron:default >>>>> # svcprop -p general_ovr/enabled svc:/system/cron:default >>>>> 2>/dev/null >>>>> true >>>>> # svcadm enable svc:/system/cron:default >>>>> # svcprop -p general_ovr/enabled svc:/system/cron:default >>>>> 2>/dev/null >>>>> # >>>>> >>>>> svcprop returns 'false' if the service is temporary disabled and >>>>> 'true' if the service is temporary enabled; otherwise it returns >>>>> nothing. >>>> >>>> >>>> >>>> >>>> But wouldn't it be nice if you could do this instead: >>>> svcdiff -s current -s running >>> >>> >>> >>> But the 'general_ovr/enabled' property is only present in the volatile >>> repository which information is not saved in a snapshot. >> >> >> >> Is there a reason it couldn't live in other snapshots and always have >> the value 'false' ? >> > > If it is always 'false' then you couldn't tell if the instance is > temporary > disabled or not...
Well it isn't always false in the volatile repository. Doesn't that have a name - running? Darren
