Perhaps someone can clarify for me what I am seeing on my system.

A. If I enable my test application and reboot, the test application is started 
automatically following the reboot [as expected]

B. If I 'disable -t' the application and reboot, it's started automatically 
following the reboot [as expected]

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].

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:
  .general_ovr/enabled boolean false
  .general/enabled boolean false
  .general/entity_stability astring Stable
  .general/single_instance boolean true

So, what else has to be set so that the application is started following the 
reboot? I am at a loss to understand the difference between doing a 'disable 
-t' on an enabled application vs. doing that on a disabled application.

Thank you in advance for any help.
Tom
 
 
This message posted from opensolaris.org

Reply via email to