Todd Pisek wrote:
On 07/ 2/09 04:06 PM, Bart Smaalders wrote:
Todd Pisek wrote:
I've had to abuse the current actuator mechanism in IPS to prevent pkg install or uninstall from removing or updating files while the file system is active.

I would like to start discussing a way to allow a service to communicate to IPS that it is currently active, preventing pkg from making any changes.

One idea we've had is to create an attribute for the entire package (to prevent endlessly specifying files/directories). This attribute would specify an SMF property and an associated failure value. Before pkg would update/remove any files, it would check to see if the property was set to the failure value. If it was, pkg would fail the update/removal.

This doesn't make a lot of sense to me....

Why not simply mark samfs components w/ reboot-needed=true?
Can you elaborate on what this does and the sequence of events?

What this will do (once we get full reboot-needed support finished) is
prevent actions w/ this set being modified in a live image; instead,
they will be applied in a clone of the current image, and a reboot will
be required to make this effective.

I'm unhappy w/ marking an entire package w/ any attribute; generally,
a change in a header file or man page doesn't require a reboot or
svcadm restart.

- Bart


--
Bart Smaalders                  Solaris Kernel Performance
[email protected]         http://blogs.sun.com/barts
"You will contribute more with mercurial than with thunderbird."
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to