I think it is more a matter of precedence, which rule is more important. Everything I know of that reads files like this, the comment starts with the # and goes to the end of the line, no continuation unless there is another # on the next line. The backslash continuation is only for lines that are read in, as soon as the parser sees the # it should ignore the rest of the line. Multi-line comments are usually enclosed in a block with definite beginning and ending sequences.
But this is probably all moot for g3. Will there be any more ganglia 2.5.x releases for maintenance purposes in case people want to take their time to switch over to g3 since it will be a major change? ~Jason On Tue, 2003-09-09 at 19:42, Robert Walsh wrote: > > I noticed one minor bug in the way gmond parses its config file when I > > inadvertently put the following in my gmond.conf file: > > > > # trusted_hosts 1.1.1.1 1.1.1.2 1.1.1.3 \ > > trusted_hosts my.gmetad.host > > > > It does not read in the trusted_hosts line. My guess is that it is > > incorrectly assuming that the comment is being continued on the next > > line. This might not be a big deal to fix since Matt mentioned once > > that g3 will probably use an xml based config system, but I thought I > > would bring it up anyway. > > This strikes me as a religious issue - one group of people will say it's > doing the right thing and another group will say it's completely wrong. > > I'm probably on the former group's side, but I don't care if it's > changed, really. > > Regards, > Robert. -- /------------------------------------------------------------------\ | Jason A. Smith Email: [EMAIL PROTECTED] | | Atlas Computing Facility, Bldg. 510M Phone: (631)344-4226 | | Brookhaven National Lab, P.O. Box 5000 Fax: (631)344-7616 | | Upton, NY 11973-5000 | \------------------------------------------------------------------/
