On Fri, Jun 05, 2009 at 04:32:39PM -0500, Todd Pisek wrote: > The way I interpreted pkg(5), was that disable_fmri would run 'svcadm > disable <disable_fmri>' before removing files. I assumed the purpose of > this was to make sure the package's daemons etc. were stopped before > removing files and IPS would not remove anything until the service > disable completed. Is this correct?
I think so (and also to give the service a chance to self-dissassemble). BTW, I hope that's a synchronous disable (or effectively so)! > If it is, I'm wondering what the use case is if the stop method can't > shutdown daemons, etc. properly. svcadm disable always stops the service if it is running. If the stop method fails then the service will still stop (its processes will be killed), and the service will be put into maintenance. > My particular package is a file system, > and the stop method can't properly complete if there are mounted file > systems. Well, presumably IPS won't be able to unload the kernel module that goes with that filesystem, so the mounts will continue to work. Nico -- _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
