On Mon, 2 Feb 2015, Rainer Gerhards wrote:
I just did it again as I could not be sure I the first one had both
destinations un-commented.
http://pastebin.com/Dz5qxbQu
That log unfortunately just covers the startup, up to the point where the
main process forked. So it is created differently than the initial snippet.
Unless you are debugging a config/startup problem, the interesting part of the
debug log is when the first log message is sent to the problem destinations.
Most of the setup for any output doesn't take place until there is a log message
sent to that output. This includes connections to remote machines, etc.
This adds some latency to the first message being output, but if you remember
that rsyslog has template based outputs, you can see how it can't always know
what outputs are going to exist before there is a log message sent to them.
David Lang
_______________________________________________
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.
