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

[Charles Lepple]

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