Eric Sproul writes: > The service has restarted correctly for me on both 006 and 014 with > this update. I'm not sure why that is though, because you're > correct that the ntp.xml file has not changed in all of the '014 > versions published. I was under the impression that the > restart_fmri actuator would only fire when the associated action was > triggered.
Yes, that's why it did not restart on my 014 box, hence I noticed. Maybe you were on an earlier rev where the manifest really did change? I guess it also restarted when Dan tested, or else he would not have mentioned that pkg DTRT. > However, if we really *do* want to restart ntp when the *daemon* > updates, then we could add a restart_fmri actuator on the > usr/lib/inet/ntpd file. Thus, whenever that file is updated, > svc:/network/ntp:default could be restarted. It's been a while since I last tried, but I think this will not work, at least not in some corner cases, e.g. when the pkg is not installed at all, and the svc:/network/ntp:default service does not exist when the pkg is installed. ISTR that pkg install will error out. Hmmm, need to test that again sometimes. :-) Regards -- Volker -- ------------------------------------------------------------------------ Volker A. Brandt Consulting and Support for Oracle Solaris Brandt & Brandt Computer GmbH WWW: http://www.bb-c.de/ Am Wiesenpfad 6, 53340 Meckenheim, GERMANY Email: v...@bb-c.de Handelsregister: Amtsgericht Bonn, HRB 10513 Schuhgröße: 46 Geschäftsführer: Rainer J.H. Brandt und Volker A. Brandt "When logic and proportion have fallen sloppy dead" _______________________________________________ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss