On Tue, 22 Jun 2010, Andre Lorbach wrote: >> -----Original Message----- >> From: [email protected] [mailto:rsyslog- >> [email protected]] On Behalf Of [email protected] >> Sent: Dienstag, 22. Juni 2010 17:10 >> To: rsyslog-users >> Subject: Re: [rsyslog] feedback requested: NEW rsyslog.conf format -- XML? >> >> On Tue, 22 Jun 2010, Andre Lorbach wrote: >> >>>> -----Original Message----- >>>> [email protected]] On Behalf Of [email protected] >>>> >>>> On Tue, 22 Jun 2010, Andre Lorbach wrote: >>>> >>>> define 'fully and correctly used' >>>> >>>> what I've suggested if valid XML, beyond that there are lots of >>>> things that could be done, and what is correct varies between uses. >>> >>> Proberly a bad term from me, "completely" is better. >>> If you use &#A, the XML Parser will automatically convert it into a > linefeed. >>> But if you use \n, we need an additional step to convert the >>> replacement character into a linefeed. >> >> however, since we are still going to support the legacy config format, we > still >> need to support replacing \n with a newline, so we don't save by changing > to >> &#A > > To my understanding the legacy config format remains and is still supported. > So I don't see the need to support legacy config format in the new format > unless you want to save one-time replace of "\n" into "&#a".
I don't see it as a one-time thing as I expect sysadmins to be doing cut-n-paste of data elements between formats (either when they are converting something, or when they are following some example from the Internet) I wouldn't object to supporting both (in case someone uses &#A in a file since it's XML), but I think it's important that strings copied from the old format work in the new format without the admin needing to remember to do a conversion. David Lang _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
