Byron Nevins writes: > I am working on adding SMF support to GlassFish. It is all working fine > but I have one question: > > Say that SMF has my service "online". I kill it externally with the > kill command. SMF notices nd restarts it for me as expected. > > Now I try the opposite: > > SMF has the service "disabled". I start the app externally. SMF does > not seem to notice. > > I think this is probably beyond the design of SMF but I would like to > verify: > > *** Is there a way for SMF to automagically notice and take control of > the externally started app? **** > > > _______________________________________________ > smf-discuss mailing list > smf-discuss at opensolaris.org
You are correct. This is beyond the design of SMF. SMF only keeps track of the services if it starts them. It uses the contract file system (man -s 4 contract) to do this. Thus, if you want SMF to be aware of the service, you should start it with the svcadm enable command. The side benefit of starting the service this way is that it will check the dependencies that you declare in your manifest. SMF will only actually start the service if all of it dependencies are satisfied. Also if there are other services that are dependent on your service, they will be started once your service starts. tom
