Re: syslog-ng problem

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

On Sun, 26 Sept 2021 at 12:43, Michael van Elst <mlelstv%serpens.de@localhost> wrote:
>
> ci4ic4%gmail.com@localhost (Chavdar Ivanov) writes:
>
> >Sep 24 01:00:00 ymir newsyslog[11908]: log file turned over
> >Sep 25 10:21:15 ymir syslog-ng[11454]: syslog-ng starting up; version='3.34.1'
> >Sep 25 10:21:44 ymir postfix/qmgr[2204]: EED9988F35: from=<>,
> >size=2719, nrcpt=1 (queue active)
> >...
>
> When newsyslog rotates logfiles, it signals syslogd to re-open the
> logfile. This is done by sending a SIGHUP signal to the pid recorded
> in /var/run/syslogd.pid.
>
> The syslog-ng package will uses the filename '/var/run/syslog-ng.pid'.
> When you configure newsyslog to use that file, it should also handle
> syslog-ng.

Thanks. My understanding is that /etc/newsyslog.conf uses
/var/run/syslog.pid for all the logfiles configured  (with the
exception of npfd.pid), so I added /var/run/syslog-ng.pd to all the
other lines. I also added newsyslog=YES to /etc/rc.conf to get new log
files upon boot.

I should have read the existing man page better - I thought it was
something to do with the new syslog-ng update...

>


-- 
----