Steve Gonczi wrote: > It looks to me, there is usually one actuator attached to some file action.
True, though that needn't be the case. You can have more than one actuator attached to an action. An actuator can be attached to any action, not just file. > I do not understand why an actuator can not just be run by itself. All components of a package must be delivered as part of an action. > I deploy a set of service xml-s, and each one (or, myb just the last > one) features the importer restart_fmri actuator, so they are imported > by the time the I am done with my "file" actions. > > At this point, it would make sense to trigger the service restart_fmri > (say, via wildcard) to restart / start all the services I have just > deployed. > > At this point, the action I want to perform is not tied to any specific > file's deployment. (All my file deployments are all done at this point) You could tag all applicable actions (file, and maybe symlink and link) with the fmri of the service you're delivering so that if any one of them changes, your service will get restarted. Note that documentation and other auxiliary files shouldn't get tagged, since they don't affect the service runtime. There was some discussion about this some months ago, in the context of the SAM/QFS packages. Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
