Mailinglist Archive: opensuse-security (192 mails)

< Previous Next >
syslogd still not logging after rotation
  • From: Michael Hase <michael@xxxxxx>
  • Date: Wed, 10 May 2000 18:32:53 +0200 (MET DST)
  • Message-id: <Pine.GSO.4.05.10005101830210.21963-100000@xxxxxxxxxxxxx>
Hi,

today we realized the problem, that syslog does not work after logfile
rotation (Suse 6.3). The aaa_base update does not correct this. Thomas
Biege from suse considered a

kill -HUP `cat /var/run/syslogd.pid`

at the end of the rotating script. This is only a workaround as
messages logged in the time between rotation of the specific file and
this statement are lost. So the protocol in /var/log/messages may
not be complete.

The update of the aaa_base package as suggested by suse has a new
problem in the script /etc/cron.daily/aaa_base_rotate_logs: the
logfiles get copied before the service is restarted. syslog has its
files open, so an open file gets copied!

The old suse 6.3 script had a mv in it, but did the commands in the
wrong order (mv, gzip, then restart service)

There is already a mechanism in this rotating script as suggested by
Michael Dirska, just add syslog in the last column of /etc/logfiles.
Important: do this for every file used by syslog.

Imho this should be fixed immediately in another update.

Michael

--
Michael Hase Six Offene Systeme GmbH
michael@xxxxxx Sielminger Str. 63
http://www.six.de 70771 Leinfelden-Echterdingen
phone +49 711 99091 62 Germany


< Previous Next >
This Thread
  • No further messages