Re: [Nut-upsuser] battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error

On 04/04/17 15.19, Arnaud Quette wrote: [cuuut] there is a Github issue: https://github.com/networkupstools/nut/issues/415 + a branch with the implementation: https://github.com/networkupstools/nut/tree/upsmon_alarm For now: - upsmon can react on the ALARM notify type, as with other

Re: [Nut-upsuser] battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error

2017-04-04 14:18 GMT+02:00 Jon Bendtsen : > On 04/04/17 14.10, Roger Price wrote: > >> On Tue, 4 Apr 2017, Arnaud Quette wrote: >> >> > [cut] > > Hi Arnaud, It seems to me that, looking out into the future, there are >> three >> things upsmon needs: >> >> 1. A

Re: [Nut-upsuser] battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error

On 04/04/17 14.10, Roger Price wrote: On Tue, 4 Apr 2017, Arnaud Quette wrote: [cut] Hi Arnaud, It seems to me that, looking out into the future, there are three things upsmon needs: 1. A fall-through of "UNKNOWN" so that all status changes, no matter how wierd, can be caught. Such a

Re: [Nut-upsuser] battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error

On Tue, 4 Apr 2017, Arnaud Quette wrote: Hi Jon, Stuart and the list 2017-04-04 1:09 GMT+02:00 Stuart Gathman : 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

Re: [Nut-upsuser] Is a timer a file?

Hi Roger, 2017-03-28 15:07 GMT+02:00 Roger Price : > Hi Arnaud, > > On Wed, 22 Mar 2017, Arnaud Quette wrote: > > The technique is very general and is to send SIGUSR1/SIGUSR2 to the >> upsd daemon. SIGUSR1 and SIGUSR2 are events just like ONBATT and ONLINE. >>