Quoth Paul Kraus on Wed, Oct 25, 2006 at 08:39:31AM -0400: > On 10/24/06, David Bustos <David.Bustos at sun.com> wrote: > >svcadm refresh is meant to commit configuration changes and notify the > >service of those changes. For syslog, this happens to be the same > >operation as close-log-files-for-rotation, which is what we really want > >to do. But from an SMF perspective, they're not the same, so logadm > >shouldn't use svcadm refresh. In particular, if an administrator were > >in the middle of making changes, and logadm refreshed syslog, then the > >changes might be committed prematurely. > > According to the man page for syslogd, whenever it receives a > HP signal it re-reads its configuration file, so I don't see how a > kill -HUP is any different from a svcadm refresh ... unless svcadm > refresh does additional things. Am I missing something here ?
Yes. Sorry; I wasn't clear: the changes which svcadm refresh commits are changes to the service's repository properties. Even if svcadm refresh didn't do that, there would be intention and specificity mismatches. logadm is trying to invoke syslogd's close-log-files-for-rotation operation. Just because the service-independent reread-configuration operation (svcadm refresh) does that doesn't mean logadm should use it. David
