I've seen discussion of deferring some actions to an SMF service[*] that
would be pinged after pkg installation (or, in the alternate root case,
would simply run at next boot).

I also noted Jordan's comment about deferred action failures, that there
should be a way to tie deferred actions to specific pkg installs and to
check their status.  I'd like to second this.

Since each service ping could potentially run multiple deferred actions
I think we'll really need a structured way to check the exit status of
each action and to log per-action messages in a way to ties back to the
actul pkg install (or remove).

I figure most actions will be scripts, so a simple CLI by which to tell
IPS that some action has started to execute, and later that it has
completed and the satus, would be good.  C and Python APIs to do the
same would be nice too.

An SMF upgrade/config/whatever method would probably also help by
distinguishing deferred actions from traditional service start/refresh.

Nico


[*]  Specific to each pkg, with a generic one for pkgs not associated
     with any service?
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to