Hi, Florian Riedl wrote: > Rainer's comment with the PID triggered a memory for me. I have tested rate > limiting in rsyslog a few years back and my first approach was a script > that calls logger. Long story short: they way logger is called, it is a new > process every time. The rate limiting as well as $RepeatedMsgReduction > check the process ID. If it differs, it is not working on the message. > > Here is the article I wrote about it: > http://www.rsyslog.com/first-try-to-test-rate-limiting/ > > It's the very same cause, just a slightly different application.
This was a very useful article, thank you Florian. <--- OT A tool like syslog_caller should be part of "diagtools" or "usertools". Replacement for "msggen" tool: -n parameter (How many messages the tool should generate) -m <Custom message> (if not set, a random message, maybe including the dynamic value $i, should be generated... but sometimes you need a tool which will always create the same identical message, therefore you need a way to overwrite...) Maybe this can go into the "logger" replacement tool? ---> I had to modify "syslog_caller.c" so that the message will always be the same, but now $RepeatedMsgReduction seems to work. Well, when set "$RepeatedMsgReduction = off" and I run "./syslog_caller -m 100" I'll get 100 "test message" lines per call. When I set "$RepeatedMsgReduction = on" I only get *1* "test message" line per call -- but no hint that rsyslog suppressed repeated messages... -Thomas _______________________________________________ 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.
