On 03/ 6/11 02:38 PM, Gary Winiger wrote:
I have a service that's been delivered in Nevada for some time.
The service manifest is not enabled by default. The service is not
in any profile. It does not need to be part of the seed.
The service is long running (not transient).
The service now needs to be enabled by default upon pkg install/update.
It can later be disabled by an admin if they do not desire its
functionality and should then not be re-enabled upon a subsequent
pkg install/update.
What might be the proper/preferred way to accomplish this?
Unfortunately, I've not kept up with all the changes in how IPS
and SMF interact. If this was going to be from an initial install,
I believe I'd have two options. Enable in the manifest or enable
in a profile (generic_*.xml).
Right now, the only answer is enable in the manifest if you want it to
be enabled on upgrade.
Currently profiles are only applied at initial install time. (We're
working on remedying that, but for now, my advise is enable in the
manifest.)
liane
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
