On 14/9/12 4:56 AM, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wednesday, 2012-09-12 at 21:49 +0200, Carlos E. R. wrote:
On Thursday, 2012-09-13 at 01:59 +0800, Otto Rodusek wrote:
add
$SystemLogRateLimitInterval 0 #$SystemLogRateLimitBurst 50 $SystemLogUsePIDFromSystem on
Ah, that means log all. Good.
It is not working... I still get complains from rsyslog:
<5.6> 2012-09-13 22:45:09 Telcontar rsyslogd-2177 - - - imuxsock begins to drop messages from pid 22554 due to rate-limiting <5.6> 2012-09-13 22:45:10 Telcontar rsyslogd-2177 - - - imuxsock lost 6 messages from pid 22554 due to rate-limiting <5.6> 2012-09-13 22:45:36 Telcontar rsyslogd-2177 - - - imuxsock begins to drop messages from pid 7540 due to rate-limiting <5.6> 2012-09-13 22:45:40 Telcontar rsyslogd-2177 - - - imuxsock begins to drop messages from pid 22554 due to rate-limiting <5.6> 2012-09-13 22:45:41 Telcontar rsyslogd-2177 - - - imuxsock lost 6 messages from pid 22554 due to rate-limiting <5.6> 2012-09-13 22:45:44 Telcontar rsyslogd-2177 - - - imuxsock lost 10 messages from pid 7540 due to rate-limiting
I'll try:
$SystemLogRateLimitInterval 5 $SystemLogRateLimitBurst 2000
Or could it be because I did a rcsyslog reload instead of restart?
- -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux)
iEYEARECAAYFAlBSSMgACgkQtTMYHG2NR9VV0wCeJS+R1D8vHsjQaVNTtR6Vs50N 9N0AnA6qbNjHsLxo4P61M9RLpO5Ee6/i =Fton -----END PGP SIGNATURE----- Hi Carlos,
Yep you're right - it worked for a while but now spewing out again. I'll be upgrading to 12.2 next week and see if the newer version of rsyslog will resolve the problem. I'm also playing around with the parameters to see if it has any effect. Best rgds. Otto. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org