On Mon, Nov 24, 2008 at 04:28:09PM -0800, David Powell wrote: > Bart Smaalders wrote: > > Ed McKnight wrote: > >> My reading of threads on this topic suggest that if my package pings an > >> SMF script (with refresh, for example) on uninstall that the invocation > >> happens before the bits delivered by the package are actually removed > >> from the filesystem. True? > > > > yes > > By "yes" I assume Bart means that services that are to be disabled on > remove are synchronously disabled before they are removed. > > And that if something is to be refreshed, it is refreshed after the > remove occurs (otherwise it's not being refreshed with the system in > its new configuration, and it would theoretically be a no-op).
And there's no synchronous refresh, so it'd have to be a synchronous disable. > There isn't a "run this service from the package you're removing > before the package is removed" mechanism. No? Why not synchronous enable followed by synchronous disable? The only problem: how to tell that service that what's happening is that a pkg related to it is being removed. That could be done by dropping some file into a deaddrop for that service, but that's not going to work when the pkg being removed is the one that delivered that service (also, better than a deaddrop: provide an API by which the service methods could query what's up). Nico -- _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
