https://bugzilla.novell.com/show_bug.cgi?id=656197 https://bugzilla.novell.com/show_bug.cgi?id=656197#c17 --- Comment #17 from Marius Tomaschewski <mt@novell.com> 2010-12-07 09:54:31 UTC --- (In reply to comment #15)
It is neither a bug in rsyslog, nor in openSUSE, but as already written in comment 8, it is a configration option and openSUSE is using the rsyslogd default setting of "$RepeatedMsgReduction off".
Question:
When a message is repeated many times and filtered out, doesn't rsyslog print a message of the type "skipped 100 identical messages", or something like that? I have seen that on openSUSE logs, time ago...
As I already wrote: - syslogd does this by default. - for syslog-ng-1.6 I wrote a patch to do it by default as well. in syslog-ng-2.0.9, there is no suppress() option doing it as in syslog-ng-3.1. - in rsyslogd it is a option with built-in default 'off'. For openSUSE-11.4 I've enabled the RepeatedMsgReduction option and I'll enable the suppress() option for syslog-ng as well in the next submit to catch this special case. Because it is an option in rsyslog (=default), I've asked in comment 14, whether I have to provide an update package with new /etc/rsyslog.conf, that enables this option or not.
If that is not so, I think it would be useful perhaps to leave messages on in factory, and filter them in the stable releases.
As to the bug being solely the fault of hpijs/services.cpp, I mildly object: a faulty program should not crash a system (disk full).
It is not possible to prohibit this. The option catches a special case only: programs that log *exactly* same message. As soon as a message differs even one bit, the message gets logged. So a user or program just need to run e.g. the following to fill up the log-disk: i=0 ; while true ; do logger "======== $((i++)) ==========" ; done ==>> Best is to always put /var/log to a separate disk. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.