Thanks for that. This option didn't throw any error and seems like
rate-limiting has stopped.
I was actually referring to this page
http://www.rsyslog.com/doc/imuxsock.html for rate-limiting and adding
"$*SysSock.RateLimit.Interval* 0" was throwing error saying syslog
couldn't understand what it means.
rsyslogd-3003: invalid or yet-unknown config file command - have you
forgotten to load a module? [try http://www.rsyslog.com/e/3003 ]
rsyslogd: the last error occured in /etc/rsyslog.conf, line
28:"$SysSock.RateLimit.Interval 0"
Can you please explain the different b/w these two types of rate-limits.
Is it like, SysSock is for socket level & the one you said is global? Also,
On 01/29/2013 01:45 PM, Radu Gheorghe wrote:
$SystemLogRateLimitBurst 0
--
Cheers,
Abhijeet R
http://blog.abhijeetr.com
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
