On Fri, 25 Jan 2013, shadyabhi wrote:
Hi David,
Turns out, it was a BUG!
It's the same as this guy here
http://kb.monitorware.com/viewtopic.php?f=36&t=11868&sid=59a959078d248e24a716d856dc5c9c0a
suffered.
Turns out, $PreserveFQDN has to be the first line in rsyslog.conf.
Actually, now that you say this, it makes perfect sense.
The way rsyslog reads it's config file is that it goes through it line by line,
implementing what that line says to do.
This has good points and bad points.
the good is that it allows you to set different config options at different
points in the file
the bad is exactly this case, if you don't set $PreserveFQDN before you load the
modules that generate the log files, they don't start up with this config value
set and you can't set it later in the file.
If someone wanted to preserver the FQDN for some sources, but not for others,
this may be the intent, but for the common case, it catches people by surprise.
A large part of the push for the v6/v7 config language changes has been around
simplifying and cleaning up exactly these sorts of options.
Thanks for reporting back on the issue.
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.
