> If you don't specify an alternative repository, it > uses libscf > unmodified, which contacts the system svc.configd. > If you specify an > lternative repository, svccfg starts its own > svc.configd on that file > and uses private mechanisms to instruct libscf to > communicate with it. > So if you use "repository /etc/svc/repository.db", > you get your own > svc.configd modify repository.db, and the system > svc.configd (which > svc.startd is listening to) doesn't see the changes. > (I suppose it > ould, but it assumes it's the only modifier, so it > doesn't check for > external changes.)
This definitely needs to make it into the manual page for current incarnation of svccfg(1M). Understanding how svccfg "repository" directive works is crucial to understanding how SMF works. Perhaps that's not necessarily achitecturally pure, but I feel that it would be useful to anyone outside of Sun who is doing any kind of work with/on SMF. > Unfortunately not. That's one of the things we want > to address with the > Enhanced SMF Profiles project in the long term and > 6509773 in the short > term. BTW, that bug was not viewable when I tried to look it up on bugs.opensolaris.org this morning. This message posted from opensolaris.org
