Greetings,
I would like to gain a better understanding of the service manipulation actuators. It looks to me, there is usually one actuator attached to some file action. I do not understand why an actuator can not just be run by itself. e.g.: 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) The man page does not spell out all the details, e.g.: can I use multiple actuators per action? Should I perform some bogus file action, such as re-setting permissions on an arbitrary file I already deployed so that I can run the service restart actuator? That would feel a bit awkward, maybe there is a better way. So why do I need a file action to hang the actuator on? TIA for any clarification. Steve Gonczi [email protected] _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
