An out-of-process implementation for the plugins would solve all such issues. But that takes time... A work-around may be to run two rsyslogd processes concurrently. Definitely not a mainstream or default config, but could be done. Also, I wonder if the kernel log works on BSD (not tested), in which case the experimental code would work there without any bad side effects (better phrased: with side-effects yet to be seen, as I said I did so far not invest any serious time in testing).
Rainer > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:rsyslog- > [EMAIL PROTECTED] On Behalf Of Michael Biebl > Sent: Wednesday, November 19, 2008 2:08 PM > To: rsyslog-users > Subject: Re: [rsyslog] rsyslogd security questions/comments > > 2008/11/19 Michael Biebl <[EMAIL PROTECTED]>: > > 2008/11/19 Michael Biebl <[EMAIL PROTECTED]>: > > > >> > >> /dev/klog could be made accessible via an ACL or a separate group. > > ^^^^^^^^^^^^ > > Argh, /proc/kmsg, I mean. > > Looks like one can't set an ACL on a procfs unfortunately. > > Michael > > > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
