Using syslog-ng instead of syslog

Using syslog-ng instead of syslog - Printable Version

+- ispCP - Board - Support (http://www.isp-control.net/forum)
+-- Forum: ispCP Omega Support Area (/forum-30.html)
+--- Forum: System Setup & Installation (/forum-32.html)
+--- Thread: Using syslog-ng instead of syslog (/thread-3708.html)

Using syslog-ng instead of syslog - FeG - 07-08-2008 06:30 PM

Hi all,

I'm using syslog-ng instead of syslog on my server (dedicated, Debian Etch, ispCP RC5) and getting errors from logrotation because in /etc/logrotate.d/ispcp it says:

Code:

/var/log/proftpd/ftp_traff.log {

  ...

  postrotate

    /usr/bin/killall -HUP syslogd

  endscript

}

Of course this will fail because no syslogd is running. This was already discussed in ticket 992, which was resolved in Changeset 1016 by deleted these three lines from the logrotate script in the Gentoo version.

I have therefor two questions:

1. Is deleting these lines the right way or should one call

Code:

/usr/bin/killall -HUP syslog-ng

Which means: Does syslog-ng needs a SIGHUP after rotating its logfiles?

2. Why was this fix only applied for Gentoo? I mean, if ispCP keeps at using syslogd, it shouldn't be changed anywhere. If we choose to use syslog-ng, it should be changed for all distributions. (Or is syslog-ng the default syslog-daemon on Gentoo?)

Thanks in advance and greetings,
FeG