Hi Brian,
Of the two choices, #1 is preferred (deep sixing non-printable config
files). Non-fatal errors allows us to make config parameters backwardly
compatible. Imagine what would have happened if html parsers wouldn't ignore
things they don't understand. What I don't understand is how the parser came
up with 60s from anything that I've seen below.
Andy
-----Original Message-----
From: Brian Bockelman
Sent: Wednesday, March 28, 2012 10:28 AM
To: xrootd-dev
Subject: UTF-8 … don't do it
Hi,
We've been tracking a nasty issue locally where the following line:
xrd.report xrootd.t2.ucsd.edu:9931 every 30s all sync
is getting ignored with the following error message:
Config warning: ignoring invalid report option '60s'.
=====> xrd.report xrootd.t2.ucsd.edu:9931 every 60s all sync
Turns out, the actual contents of this line were:
xrd.report xrootd.t2.ucsd.edu:9931\xc2\xa0every 30s all sync\n
I believe C2-A0 is the UTF-8 encoding of a space character. Grumble.
Two proposals:
1) The config file parser should refuse to accept config files with
non-printable characters.
2) Invalid options should become fatal, otherwise they may get ignored for
years by the site admin.
Thoughts?
Brian
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
|