MonitorWare Knowledge Base

Hello again. The FreeBSD rsyslog wiki page http://wiki.rsyslog.com/index.php/FreeBSD mentions a klog workaround in the form of logger(1), but gives no further details. Can anyone elaborate on this? I'm testing rsyslog for deployment in a production environment, and hesitate to jump to the branch with a built-in fix for the klog bug since it's still in dev...is there any other option?

Thanks in advance for the help.
-HKS

• Custom written rsyslog.conf?
• Maintenance Contract?
• Installation support?

If you are using a recent version rsyslog (>= 3.16), rsyslog has native support for klog on (Free)BSD and the logger workaround is no longer necessary.

The wiki is outdated. Just make sure, the imklog module is compiled and load it via
$ModLoad imklog

HTH,
Michael

Thanks. I've moved to 3.17.4 and no longer need the workaround. It makes me a little nervous running on beta code, but so far everything seems solid...

-HKS

I think you can relax: the current beta branch will very soon turn into the next stable. I expect next week. Please note that there was a refresh (with a minor fix), so we are right now at 3.17.5.