2015-03-10 21:10 GMT+01:00 Troels Arvin <[email protected]>: > Hello, > > Rainer Gerhards wrote: > > I think what happens here is that the message > > is sent via TCP syslog, and there LF is the *frame delimitor*. So we > > actually have a protocol error in this case - the LF indicates that a > > new message begins. As such, it is not part of the message itself. > [...] > > I don't know whether TCP is being used. But after having looked more > closely, it seems like it might be the server's own snmptrapd which is > relaying traps which include newlines. So one might argue that I should > look for a solution within snmptrapd: But it would be nice with a > solution which makes sure that rsyslog never places a newline in > /var/log/messages -- except as a message delimiter, of course. >
Pls read my previous message carefully: I think the LF *is* the message delimiter. Rainer > > -- > Regards, > Troels Arvin <[email protected]> > http://troels.arvin.dk/ > > _______________________________________________ > 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. > _______________________________________________ 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.
