On Apr 5, 2012, at 1:22 AM, Rainer Gerhards wrote: >> The issue is the repeating of identical information throughout the >> rsyslog.conf. With a few hundred lines, and dozens of references to >> the same loghost, same port, etc it becomes somewhat silly to make >> changes. It would be very useful to be able to define the hostname, >> port and potentially the format in a single place. (as syslog-ng >> allows) > > This dynamic hostname is not supported. Actually, it's the first time someone > asks, but I have to admit I see some value in it. > > However, is > s/oldname/newname/g > such a problem? > > Anyhow, if you send a patch, I am definitely interested in adding it.
We ran into this because we are sending to the same host on a different ports using different templates. We went to move one of these services to a different host, and someone did exactly s/hostname/newhostname/ not realizing it affected *all* services on that host, and broke the rest of them. Fixing this required a slow and careful review of the entire file to determine which ones should be where. It's also quite easy to write a rule and send the data to the wrong location be accident. Scoping around inside the file to determine port and template involves human estimation, which gets different results from different people. Macros like "UsageDataServer" and "TracefileServer" make it a lot easier to get the right choice ;-) I will say that this is high enough priority to rate coding a fix for it, but I also don't see much availability in my upcoming schedule to get to that. If someone else is willing to tackle this I'd appreciate it. If not I'll try to get to it when my schedule opens up. -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/
