Tom Dillard writes:
> C. If I disable the application, then do a 'disable -t' on it, then
> reboot, the application does NOT start following the reboot [not as
> I expected].
Just to clarify ... for this case, you ran these two commands:
svcadm disable <FMRI>
svcadm disable -t <FMRI>
and then rebooted, right? If so, then why were you surprised to see
that the application doesn't start after a reboot? The first command
disables the application -- both now and after a reboot. The second
command just disables it now, leaving it still disabled after the
reboot.
> I did a 'svcprop <FMRI>' of my test application in scenario 'B' (after
> disable -t but before the reboot) and saved that output. I then captured the
> same output for scenario 'C'. The outputs are the same (except for expected
> differences such as pid and timestamp values). Both had these fields the same:
svcprop shows you a composite of running and saved state. I think you
want "-c" to look at the state for next reboot.
--
James Carlson, KISS Network <james.d.carlson at sun.com>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
