Many Thanks for your reply.
Syslog-ng is a bit heavy-duty but I find it easier getting to grips
with the structure and logic of the config file than with syslogd.
Also could never really get the logs split out with syslogd to the
extent I can with syslog-ng. Was not aware of the improvements to
syslogd because I have not been working with it for a few years now,
maybe it is time to take a look again.
Cheers,
Christopher
Since OpenBSD 5.6, local logging uses sendsyslog(2) which doesn't use
/dev/log.
Fix #1: run syslogd(8) and have it forward messages to syslog-ng
(either using a network socket or some arrangement with a command
pipe).
Fix #2: modify syslog-ng to use the procedure described in
sendsyslog(2)
and used by syslogd to handle the new klog mechanism. (Basically, open
/dev/klog and use an ioctl).
Do you even need syslog-ng? There have been many improvements to the
standard syslogd in recent releases.
No comments:
Post a Comment