Is there way to configure rsyslog instance to use its own programname? For example rsyslog-net or rsyslog-lin for appropriate instances which have different listen ports open. As those usually run on the same host, the error messages are logged under "rsyslog" and it is hard to decide what message is from which instance. One way for dealing could be to create link /usr/sbin/rsyslogd-lin pointing to /usr/sbin/rsyslogd and starting instance with calling this link. That will result in rsyslogd-lin being used as programname. Is there other way for dealing with it in rsyslog configuration only?
In other case it seems those internal rsyslog messages are duplicite (once logged with full syslog-tag with PID and secondly with msg only). Is there some way to supress duplicite logging of these messages? Feb 12 12:12:13 syslog01 rsyslogd[10891]: rsyslogd: imptcp imptcp: message received is at least 1536 byte larger than max msg size; message will be split starting at: "1011322,"UserFingerprint":null,"" [v8.1901.0] Feb 12 12:12:13 syslog01 rsyslogd: imptcp imptcp: message received is at least 1536 byte larger than max msg size; message will be split starting at: "1011322,"UserFingerprint":null,"" [v8.1901.0] Thank you. -- Peter _______________________________________________ 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.
