Comment 3 for bug 224791

On Wed, 2008-04-30 at 16:30 +0000, Arnaud Quette wrote:
> 2008/4/30 Al Grimstad <email address hidden>:
...
> 2 things:
> - upsmon only reports things it catches. This means that it won't
> report a low battery status by itself, but only if it has been
> reported by the driver and so upsd. And the low battery is reported
> through "ups.status=LB".

I'm sure that's all true, but upsmon is doing a WALL on low battery and
I've configured it not to do that. At least I left the LOWBATT
configuration as the default, whatever that is. I suppose I should go
check the docs to see if I can configure LOWBATT to do something else,
such as ignore totally. Anyway, just because the apcsmart driver might
be acting up, I don't think upsmon is absolved of guilt.

> So I would be in favor of a driver bug. To catch this, you'll have to
> reproduce it while running the driver in debug mode (using -DDD).
> - upsmon, as upsd, will only honor configuration changes if it has
> either been restarted or reloaded.
> so either using "upsmon -c reload" or "invoke-rc.d nut restart"

I need a bit of help to do this. Suppose I just hack /etc/init.d/nut and
change the upsdrvctl start line to add the -DDD argument? And report
whatever upsdrvctl spits out about the time I get the next WALL? -- al

> -- Arnaud
>
>
> --
> Linux / Unix Expert R&D - MGE Office Protection Systems - http://www.mgeops.com
> Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
> Debian Developer - http://people.debian.org/~aquette/
> Free Software Developer - http://arnaud.quette.free.fr/
>