Hi, this is _no_ bug, it`s a Feature ;-))) The crash of syslogd can be detected by Management Tools, so that the Administrator can react. Otherwise, there might be the ability to hide hacking by making files _not_ writable. If you want to change this, try out treating the files as pipes ( put a | in front of the Filename ) Greetings also Dirk
-----Original Message----- From: Dirk Mueller [mailto:dmuell@gmx.net] Sent: Friday, June 06, 2003 5:10 PM To: suse-security@suse.com Cc: Sebastian Krahmer Subject: Re: [suse-security] SuSE Security Announcement: cups (SuSE-SA:2003:028)
On Fre, 06 Jun 2003, Sebastian Krahmer wrote:
- syslogd Dirk Mueller reported a problem to SuSE Security that
syslogd fails to
write to a logfile if file size (u)limits set by the
administrator are
being exceeded.
Actually I reported that syslogd crashes when _one_ of the logfiles fails to write. Of course its not a prolem per se when one of the syslog files exceeds 2GB filesize limit / ulimit and stops writing to it.
-- Dirk
-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here