> On 2017/11/29 08:41, chrisb wrote:
> > @version: 3.9.1
> > source s_local {
> > unix-dgram("/dev/log");
> > };
>
> 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
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
On 2017/11/29 08:41, chrisb wrote:
> @version: 3.9.1
> source s_local {
> unix-dgram("/dev/log");
> };
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
chrisb [2017-11-29, 08:41:25]:
> Hello forum members,
>
> Having spent a couple of weeks on this problem I thought someone might be
> able to help getting syslog-ng 3.9.1 to write log files on OpenBSD 6.2. This
> really is a pain in the back-side.
>
> The O/S was a fresh install, then syslog-ng
Hello forum members,
Having spent a couple of weeks on this problem I thought someone might be
able to help getting syslog-ng 3.9.1 to write log files on OpenBSD 6.2. This
really is a pain in the back-side.
The O/S was a fresh install, then syslog-ng and lastly BIND. No other
packages except
