Bugzilla – Bug 577
need service action for smf(5) manifests
Last modified: 2008-10-10 22:40:31 UTC
You need to log in before you can comment on or make changes to this bug.
We need a service action to simplify delivery (and removal) of smf(5) services delivered via manifests in packages. The initial functionality of the service action should be 1. Install/remove/update service and instances based on manifest contents, and 2. Register the service-package relationship in an index.
I've started working on this; there are a couple of subtleties to note: * a manifest file can deliver more than one service * addition/removal/upgrade to a live root image needs to run appropriate smf commands - see [ir].manifest files in ON Nevada gate * moving manifests between packages appears as a removal and then a installation of a new manifest. This will delete user customizations until support for this goes into smf profiles project, so for now manifest migration between pkgs should be done in non-live images. - Bart
*** Bug 574 has been marked as a duplicate of this bug. ***
*** Bug 560 has been marked as a duplicate of this bug. ***
This turns out to be fairly simple to implement w/ a subclass of the file action. The only additional attribute is fmri; this is required and is the one or more fmris delivered by the manifest. The inclusion of the file hash via subclassing means the service action will be updated whenever the manifest changes; this will insure that modifying the manifest will cause it to be re-imported on a live system. The fmris are also indexed so that searching for which package delivers a service is simple.
*** Bug 1413 has been marked as a duplicate of this bug. ***
Fixed in 584:22bc748edce6