Actuators (the *_fmri tags, in this case) are only run when the actions
they're attached to change (or get added or removed, as appropriate).  So
if you put them on an action that never changes, then they'll only be
triggered on installation and/or removal.  If you put them on an action
that only changes some of the time, then they'll only be triggered on
upgrade some of the time.

Ideally, you'd put the actuator tags on exactly the set of actions that,
when changed, require the service to be restarted (the executable, for
instance, but not, say, the man pages).

Note that the set action delivering the "pkg.fmri" attribute is just
another action like any file action, in that it gets added, upgraded, and
removed.  And it's (pretty much) guaranteed to change every time the
package is updated, so you can stick actuators on that and see them trigger
every time.  It's gross overkill in most cases, but may be useful for
testing.

Danek
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to