[Nut-upsdev] Bug in file parsing of ups.conf

Doug Parsons doug at parsonsemail.com
Sat Jul 11 21:43:54 UTC 2009

I do not recall but I don't think so. All the lines in the file were the 
same but I had added several to the end with a cut and paste. The pasted 
lines had what appeared to be a space added to the end of each line. There 
is a chance that it was a non printable character. Once I deleted each of 
the characters the file parsed properly. I think it would be safe to close 
this considering that no others have confirmed this and the age of the 


----- Original Message ----- 
From: "Charles Lepple" <clepple at gmail.com>
To: "Doug Parsons" <doparsons at earthlink.net>
Cc: "nut-upsdev" <nut-upsdev at lists.alioth.debian.org>
Sent: Thursday, July 09, 2009 10:26 PM
Subject: **SPAM** Re: Bug in file parsing of ups.conf

> On Mon, Oct 23, 2006 at 9:41 AM, Doug Parsons<doparsons at earthlink.net> 
> wrote:
>> It turns out that there is a bug in the parser for the ups.conf file that 
>> if
>> the description contains a space as the last character the next entry 
>> will
>> not be recognized and will fail to start. Once I removed the spaces from 
>> the
>> last four enties (21 to 24 thus 21 being the last to load) all seems to 
>> be
>> well.
> Doug,
> What syntax were you using for these lines?
> Did you have double-quotes around the descriptions?
> Arjen was unable to reproduce this bug:
> https://alioth.debian.org/tracker/?func=detail&atid=411542&aid=304024&group_id=30602
> -- 
> - Charles Lepple

More information about the Nut-upsdev mailing list