Current time: 05-18-2024, 12:45 AM Hello There, Guest! (LoginRegister)


Post Reply 
Using syslog-ng instead of syslog
Author Message
FeG Offline
Banned

Posts: 222
Joined: Aug 2007
Post: #1
Using syslog-ng instead of syslog
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
07-08-2008 06:30 PM
Find all posts by this user Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)