Michel wrote: > Hello, > > Is there a way to configure a service to start on the next system reboot > without having to execute "svcadm enable" nor putting a file in > /var/svc/manifest.
I can't think of one off-hand, let's say the service is running, you can do a "svcadm disable -t <service>", which will turn it off for now, but will start again at next boot. Somehow, I don't think this is what you intend to do. You are probably in a situation where you just installed the box, and you want the installed state to be "disabled", but after you straighten everything out and do a reboot, you want to service to come up without having to mess with it at all. Right? The first part is easy; put this line in the manifest: <create_default_instance enabled="false"/> From what I know, there's no flag in SMF that says "enable me at next boot." You'll have to enable the service manually. > My understanding is that the deleting the service at a later date will not > only require doing a svccfg delete but will also require deleting the file > from /var/svc/manifest. Actually, you don't need to delete the manifest. Try it. Delete some service, like http-apache, and leave the manifest there. SMF won't pick it up again. EXCEPT if you do a repository restore from seed, then SMF goes back to reading and importing every manifest it finds. CT
