Nicolas Williams wrote: > On Tue, Jan 20, 2009 at 02:20:08PM -0800, Kohsuke Kawaguchi wrote: >> Speaking of logadm, it would be nice if logadm can read configuration >> from not just one file but from /etc/logadm.d/* > > Or from SMF -- each service could have its own log rotation > configuration. Fewer writable files in /etc -> better.
Yeah, that'll work for me, too. >> When I package my daemon for Solaris via pkg(5), I can't currently >> auto-configure logadm, because I have to modify logadm.conf. > > You could do it by delivering a service whose start method adds the > necessary lines to logadm.conf if they are missing. But things get > complicated on uninstall. Somehow it didn't feel right to use SMF for running one-off things like this. It feels like a hack to work around the lack of script support in IPS. Are there precedents in Solaris that do this kind of things? > Also, this is probably a good reason for having a single service to run > this sort of self-assembly: what if multiple such services compete to > edit logadm.conf? There's no locking convention they could use! A > single service that serializes self-assembly would solve that problem > (though it might slow the first post-install boot). > > Nico -- Kohsuke Kawaguchi Sun Microsystems http://weblogs.java.net/blog/kohsuke/ -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3282 bytes Desc: S/MIME Cryptographic Signature URL: <http://mail.opensolaris.org/pipermail/smf-discuss/attachments/20090120/ed99a5eb/attachment.bin>
