Quoth Tom Dillard on Tue, Jan 16, 2007 at 02:37:14PM -0800: > I have a daemon I want to start. The dependencies show up as follows. > I want the system to reach the multi-user milestone before trying to > start this service. There is no service defined that depends on this > service, BTW. > STATE STIME FMRI > online Jan_15 svc:/system/filesystem/local:default > online Jan_15 svc:/system/system-log:default > online Jan_15 svc:/milestone/multi-user:default > > The system boots up and the service starts just fine. I was playing > around with changing milestones, and changed from multi-user-server to > multi-user with: > # svcadm milestone multi-user > > I was surprised that my service was stopped. Why did changing from > multi-user-server to multi-user stop my service? After changing > milestones, the above-listed dependencies all still show up as > "online".
Because that's the definition of svcadm milestone: stop all services outside of the milestone service's dependency tree. Otherwise, we wouldn't be able to implement runlevels properly. You'll note that your service has been temporarily disabled. You can re-enable it if you'd like. David
