Guyang Mao wrote:
> Package: sysklogd
> Version: 1.4.1-15
> Severity: important
>
> It appears that while the init script for sysklogd is correct in sending
> signal 1
> (SIGHUP) to the syslogd daemon, syslogd can reach a state while the logs are
> being
> rotated (with massive CPU and disk usage at such a point in time because
> every other
> thing on the box is getting called at once) that it will not process the
> SIGHUP and
> close and reopen the current logfile.
>
> $ ls -al /var/log/syslog*
> -rw-r----- 1 root adm 0 Oct 24 06:37 /var/log/syslog
> -rw-r----- 1 root adm 9118591 Oct 25 01:47 /var/log/syslog.0
> -rw-r----- 1 root adm 4135131 Oct 23 11:30 /var/log/syslog.1.gz
> -rw-r----- 1 root adm 29 Oct 22 12:53 /var/log/syslog.2.gz
> -rw-r----- 1 root adm 29 Oct 20 09:04 /var/log/syslog.3.gz
> -rw-r----- 1 root adm 29 Oct 19 09:50 /var/log/syslog.4.gz
> -rw-r----- 1 root adm 470860 Oct 15 06:35 /var/log/syslog.5.gz
> -rw-r----- 1 root adm 485289 Oct 14 06:40 /var/log/syslog.6.gz
> -rw-r----- 1 root adm 64828 Oct 10 2002 /var/log/syslog.7.gz
Are yo usure that you are using the log rotation facility from sysklogd
and don't use logrotate upon that?
The reason I ask is that the above scenario cannot happen with the
setup from the Debian package.
a) savelog is called to rotate logfiles in the following way:
savelog -g adm -m 640 -u root -c 7 $LOG >/dev/null
This call will *not* create the new log file but only rename
the current one to $LOG.0, rename the old $LOG.0 to $LOG.1
and compress it etc. pp.
b) syslogd will create the new log file $LOG after it has
received a SIGHUP, but will then log to that new file instead
of the old one as well.
For detailed signal processing, please take a look at the code
and point me to potential problems.
Regards,
Joey
--
Every use of Linux is a proper use of Linux. -- Jon 'maddog' Hall
Please always Cc to me when replying to me on the lists.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
