Hi Jon, Stuart and the list 2017-04-04 1:09 GMT+02:00 Stuart Gathman <stu...@gathman.org>:
> On 04/03/2017 07:03 PM, Gene Heskett wrote: > > > > But it does that because you have tried to get 12 years out of a gell > > cell battery that is doing really really well if you get 4 years out of > > it. I am not saying you should do that _now_, without first replacing > > that thoroughly boiled dry battery, but as something you should set it > > up to do once you have a serviceable battery set installed in it. That > Absolutely. But as you say, that is NOT recommended for the original > poster *now* until he replaces said dead battery > (I actually recommended replacing the entire UPS to get an AVR model). > >>>> We want the ALARM that the nut driver is > >>>> generating, and upsd is passing on - to be acted on in some way by > >>>> upsmon. Which NOTIFYCMD is run when there is an ALARM? > Have you specified that in your upsmon.conf? > > And that is the question of the hour. How do you specify that? Note > that this is not the REPLBATT status we are talking about. > It's true that upsmon doesn't deal with ALARM, and that's definitely something missing. What about adding a <notify type> "ALARM" to upsmon (and its .conf), and have it processing like other notifications? That would mean to you can have WALL / SYSLOG notifications, along with EXEC reaction if NOTIFYCMD is set. cheers, Arno -- Eaton Data Center Automation Solutions - Opensource Leader - http://42ity.org NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.fr
_______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
