On 10/23/06, Doug Parsons <[EMAIL PROTECTED]> wrote:
Version 2.0.4 on CentOS (RHEL 4)
A quick check indicates that this bug probably affects the trunk as well.
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.
Thanks for following up on this. I have created a bug entry so we don't forget: https://alioth.debian.org/tracker/index.php?func=detail&aid=304024&group_id=30602&atid=411542 -- - Charles Lepple _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
