Hello, > -----Original Message----- > From: Jean Delvare [mailto:khali at linux-fr.org] > Sent: Wednesday, August 09, 2006 1:13 PM > To: Calabro, Anthony > Cc: LM Sensors > Subject: Re: Flex Scanner Jammed Problem > > Hi Anthony, > > > Very interesting results... When I turned off the %option > nodefault, > > it showed me everyhting that was happening incorrectly in > the parsing, > > and the way I finally made it run without error and > correctly work, I > > had to put the in0 in quotes also. Ex: "in0". That way a > label lin > > looked something like this: > > > > label "in0" "VCore 1" > > label "in1" "VCore 2" > > > > Doing this causes sensors -s to run without error and also now > > displays the correct labels when you run sensors... Im > still messing > > around and trying different things to attempt to figure out > why this > > is happening or if there is anything else going on here. > Ill keep you > > up to date on what I find out. > > Wow. It is known that labels need to be quoted when they do > not begin with a letter, but for regular ones like "in0" > that's completely new to me. I really wonder what causes your > version of libsensors to behave like this. > > What about my question on the locale you use? Locale is en_US.UTF-8 > > Anyway, thanks for keeping us informed, this is really appreciated. > That way we may help if other users report a similar problem. It seems that the only thing the parser recognizes are lm_sensors keywords (label, compute, set), but only if they are in the first position on the line. The sample sensors.conf will not work for me with the spaces in front of the terms. I get Invalid Keyword errors. In a compute line, I havent figured out how to make it process without error, I get syntax errors on the computation part of the line, if it put it into quotes, I get an unexpected EOL error. > > -- > Jean Delvare > >
