How do I get a service to be enabled only on a reboot?

Question

Hi!
Here's what I'm trying to do:
I have a transient service, which makes configuration changes on the system early in the boot process. However, when I install(import in SMF) this service on a system, I do not want it to run right then as it is too late to make those configuration changes on a running system. I only want it to run at boot time on the next reboot.
Options I've considered:
Option A:
1. Create a manifest with create_default_instance_enabled=true
2. Put my xml file in /var/svc/manifest/site/mysvc.xml
I do not want to import this at install time. On first reboot, it picked it up. After that, during testing, I deleted it from the repository, left the service in /var/svc/manifest/site/mysvc.xml, and rebooted, SMF didn't pick it up.
Option B:
If I instead have a manifest with create_default_instance_enabled=false, and import this.. How do I then make SMF create an instance of this service ONLY at boot time.
I've seen other posts which talk about putting your manifest in /var/svc/manifest/site/mysvc.xml or in /var/svc/profile/site.xml. I'm not sure what the difference is between these 2. Unfortunately, I haven't found any documentation on this.
I'd greatly appreciate some pointers on getting this right.
Thanks!!
pramam

Answer 1

Option A:
1. Create a manifest with
create_default_instance_enabled=true
2. Put my xml file in
/var/svc/manifest/site/mysvc.xml
I do not want to import this at install time. On
first reboot, it picked it up. After that, during
testing, I deleted it from the repository, left the
service in /var/svc/manifest/site/mysvc.xml, and
rebooted, SMF didn't pick it up.Okay.
Option B:
If I instead have a manifest with
create_default_instance_enabled=false, and import
this.. How do I then make SMF create an instance of
this service ONLY at boot time. I think you could use svccfg to set the :default general/enabled to 'true'. That wouldn't make it run, but it would try to run on restart.
I've seen other posts which talk about putting your
manifest in /var/svc/manifest/site/mysvc.xml or in
/var/svc/profile/site.xml. I'm not sure what the
difference is between these 2. Unfortunately, I
haven't found any documentation on this.The first is for your manifest. That describes your service. You'll notice that most sun services are not enabled in the manfest.
The second is a profile. A profile is brought in usually at first boot to configure a system. It may enable or disable services. Notice that there are two "generic" profiles. One turns on most things, one keeps a lot of stuff turned off.
There are 3 site profiles that can be brought in automatically: generic, platform, and site. You can create a site.xml and the first boot that finds it will load it. So at jumpstart time you can put manifests you need in the manifest area and enable/disable what you want by the site.xml.
If you use a site.xml at jumpstart time, you can't use it later to modify things.
Darren