Running S10, pretty recent, we've noticed the following behaviour: The 'svcadm restart' command doesn't always work, and often leaves our services in maintenance.
The problem seems to be that a restart does a stop followed by a start, and if the stop fails (the process doesn't die cleanly, so then smf comes along and kills the process) then the service is immediately put into maintenance with (apparently) no attempt to start it back up. In terms of availability, this is the wrong way round, as it has taken crucial services offline for us (and without any indication to the user). Why doesn't it try to start the service back up even if the stop fails? Or is there some other way of telling it that it's OK if the stop method failed? (The application is tomcat, which doesn't always shut down when you ask it to nicely.) -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
