Mailinglist Archive: opensuse-security (601 mails)

< Previous Next >
Re: [suse-security] Problems with /var/log/messages
  • From: Roman Drahtmueller <draht@xxxxxxx>
  • Date: Wed, 2 Aug 2000 12:01:45 +0200 (MEST)
  • Message-id: <Pine.LNX.4.21.0008021159070.1189-100000@xxxxxxxxxxxx>
>
> I'm having the following problem:
>
> Whenever cron gzip's my messages file, all logging to the "new" messages file
> is stopped, no information is entered. The only solution I found sofar is
> rebooting the machine, there has to be a simpler solution !
>
> Best regards,
>
> Geert-Jan de Laat

There is. Either "kill -1 `pidof syslogd`" or upgrade the package
aaa_base.

The problem is that the syslogd only opens the logfiles once. If you
remove one of the logfiles, syslogd will happily continue writing into
it. This isn't wrong since it's the admin's fault if he removes files.

Some versions of the logfile rotation parts of the daily cron scripts
didn't take this behaviour into account, newer do it again.

Thanks,
Roman.
--
- -
| Roman Drahtmüller <draht@xxxxxxx> // "Caution: Cape does |
SuSE GmbH - Security Phone: // not enable user to fly."
| Nürnberg, Germany +49-911-740530 // (Batman Costume warning label) |
- -


< Previous Next >
References