Displaying 3 results from an estimated 3 matches for "remig".
Did you mean:
remi
2025 Apr 02
0
wrong NOTIFYTYPE always ONBATT on upssched TIMER ?
...ist at
> nut-upsuser-owner at alioth-lists.debian.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Nut-upsuser digest..."
>
>
> Today's Topics:
>
> 1. wrong NOTIFYTYPE always ONBATT on upssched TIMER ? (RemiG)
> 2. Re: wrong NOTIFYTYPE always ONBATT on upssched TIMER ?
> (Jim Klimov)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 1 Apr 2025 17:22:54 +0200
> From: RemiG<mailing-nut at dbmtechnologies.com>...
2025 Apr 02
2
wrong NOTIFYTYPE always ONBATT on upssched TIMER ?
...different NOTIFYTYPE values and none is "TRUE".
* Oh, NOW I think I get what you meant:
Apr 1 17:18:14 upssched[8783]: Event: LINE-STATUS-5
Apr 1 17:18:14 upssched-cmd-received-NOTIFYTYPE: ONBATT
Just in case, which NUT version is involved?
Jim
On Tue, Apr 1, 2025 at 5:42?PM RemiG <mailing-nut at dbmtechnologies.com>
wrote:
> HI
>
> i'am using schema upsmon call : NOTIFYCMD /sbin/upssched
>
> and this part of upsschede strategy (working fine)
>
> device.model: Ellipse ECO 650
>
> root at ---:~# cat /etc/nut/upssched.conf
> # Network U...
2025 Apr 01
1
wrong NOTIFYTYPE always ONBATT on upssched TIMER ?
HI
i'am using schema upsmon call : NOTIFYCMD /sbin/upssched
and this part of upsschede strategy (working fine)
device.model: Ellipse ECO 650
root at ---:~# cat /etc/nut/upssched.conf
# Network UPS Tools - upssched.conf sample file
CMDSCRIPT /opt/nut/bin/upssched-cmd
PIPEFN /var/run/nut/upssched.pipe
LOCKFN /var/run/nut/upssched.lock
#