2016-12-01 13:06 GMT+01:00 mosto...@gmail.com <mosto...@gmail.com>:
> El 01/12/16 a las 12:55, Rainer Gerhards escribió:
>> 2016-12-01 11:54 GMT+01:00 mosto...@gmail.com <mosto...@gmail.com>:
>>>> because a syslog message contains tag.
>>> mind-blowing explanation :P
>> Well, as the property is already there, why would you like to have a
>> config parameter for something that by definition will never be
>> needed?
> A RFC 3164 formatted message contains a tag, no matter if it's read from
> file or it arrives from socket.
> Hence, there's no need to have a TAG property for any of them.

mails crossed

> A message without TAG (malformed RFC 3164 message), no matter if it's read
> from file or it arrives from socket, won't have a tag
> Hence, setting it only for imfile won't fix it for socket modules.

I am not ready for this discussion again. In rsyslog, rfc3164 messages
always have a tag. See previous lengthy discussions ;-)

rsyslog mailing list
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 

Reply via email to