OpenSolaris

Category
   utility
Sub-Category
   smf
Description
   At the user request (either "init 6" or an explicit "svcadm disable"), SMF shuts down the parent service BEFORE it tries to shut down its dependents. This equates to stopping a database before stopping the application server that depends on it.
SMF should stop all dependents first.
A full discussion can be found here:
http://forum.sun.com/jive/thread.jspa?messageID=328895
Frequency
   Always
Regression
   No
Steps to Reproduce
   Create two services, A and B, where B is dependent on A.
Run:
# svcadm disable A
Expected Result
   svc offlines B first before disabling A.
Actual Result
   svc disables A then tries to disable B.
Error Message(s)
   
Test Case
   
Workaround
   It is possible to add the following to the stop method of the dependency, for example a database:
if [ `svcs | grep -c app_server` != 0 ]; then
     svcadm disable -st app_server
fi
Submitter wants to work on bug
   No
Additional configuration information
For system/zone shutdown, this is fixed in Solaris nevada, build 12 by 6207705.
What's left is the request for shutdown of dependents before a "svcadm
disable" takes effect.
"SMF should stop all dependents first."

This is not correct for "exclude all" dependents.

N/A

N/A