On Tue, May 6, 2014 at 3:18 PM, Thomas D. <[email protected]> wrote: > Hi, > > Rainer Gerhards wrote: > >> 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... > > > > Did you send a different message? > > First I run syslog_caller without modifications, so the messages are > different due to the used $i variable. > > But I also changed > > syslog(sev % 8, "test message nbr %d, severity=%d", i, sev % 8); > > into > > syslog(sev % 8, "test message nbr"); > > The changed message was reduced (only one message was logged to disk), > but as said, there was no "last message repeated N times" message I also > expected to see. > > Yeah, I meant if you send one different message to /dev/log after that test. Because a message that's different is (traditionally) the trigger to output that "last message repeated n times" message. If it is always the same, it keeps counting.
Rainer _______________________________________________ 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.
