similar to: Proposal for technique to stop a timer at any moment

Here is patch 1 of 2. Roger diff -rup nut-2.7.4.orig/clients/upsmon.c nut-2.7.4.dev/clients/upsmon.c --- nut-2.7.4.orig/clients/upsmon.c 2015-12-29 13:08:34.000000000 +0100 +++ nut-2.7.4.dev/clients/upsmon.c 2016-07-01 09:46:21.567766415 +0200 @@ -525,6 +525,18 @@ static int get_var(utype_t *ups, const c numq = 2; } + /* Subcommands for polling SIGUSR1, SIGUSR2 RP */ + if (strcmp(var,

Dear list, I would like to propose a set of patches which make it possible for a upssched-cmd script to stop a timer at an arbitrary moment. If you find this of interest, I will submit a set of patches to 2.7.4. Roger Introduction ------------ The comments at the top of upssched.c say << * timers can be cancelled at any time before they trigger >>. It would be very useful if

Hi Roger 2017-03-21 19:34 GMT+01:00 Roger Price <roger at rogerprice.org>: > On Tue, 21 Mar 2017, Arnaud Quette wrote: > > Hi Roger, >> >> reviving this discussion, since we have a Github ticket for 2.7.5: >> https://github.com/networkupstools/nut/issues/293 >> > ... > >> I've made some additions to clarify things on the timer, and complete

Hi, I have problem with upssched on windows. Upssched is not executed. I have 2 scripts, 1 for notification in upsmon and second for scheduling in upssched. Monitoring is working fine, script write to log. I'm using binary windows installer 2.6.5-6 from NUT. Here are my configs: --- nut.conf MODE=netclient --- upsmon.conf MONITOR ups_1000 at 192.168.3.95 1 <user> <password> slave

I've recently moved from installing NUT from source to installing NUT from the FreeBSD package (FreeBSD 9.1). One would think that I might have learned not to change anything, but I made the change. And here is my tale of woe..... My first question is: is it possible to simulate a "UPS is on battery" state? Some background: UPS comm port is connected to and monitored by

Ok, I am running NUT in dummy mode. I have added a new ups in ups.conf [dummy] driver = dummy-ups port = upsc.dev desc = "dummy ups for testing purposes" upsc.dev has been generated by exporting the Elit configuration. I have added the monitor line in upsmon.conf and the "exec" flags (all the events) MONITOR dummy at artu 1 user pass master SHUTDOWNCMD

I have only RS-232 on the box (meanwhile, it was manufactured on march of 2011) Here is my configs: nut.conf: * * MODE = netserver ups.conf: * * [KIN1500] driver = powercom port = notUsed desc = "Powercom KING PRO KIN-1500AP RM" upsd.conf: * * LISTEN 192.168.1.2 3493 upsd.users: * * [monuser] password = xxxxxxxx upsmon master

On Tue, 21 Mar 2017, Arnaud Quette wrote: > Hi Roger, > > reviving this discussion, since we have a Github ticket for 2.7.5: > https://github.com/networkupstools/nut/issues/293 ... > I've made some additions to clarify things on the timer, and complete the script: > https://github.com/networkupstools/nut/compare/upssched-doc?expand=1 Hi Arnaud, Your change to the

Hello. I've tried to configure Windows (complete port, Beta): Windows MSI installer 2.6.0-1 with my Powerware 5115 connected via USB port but have no luck. Here is my config files: *nut.conf:* MODE = netserver *ups.conf:* [PW5115] driver = bcmxcp_usb port = notUsed desc = "PowerWare 5115" *upsd.conf:* LISTEN 192.168.1.12 3493 *upsd.users:* [monuser]

On Mon, 3 Jul 2017, Andrea de Lutti wrote: > MONITOR dummy at artu 1 user pass master > SHUTDOWNCMD "/sbin/shutdown -h +0" > NOTIFYCMD /usr/local/bin/upssched-script Hi, As far as I can see, what you are getting in syslog corresponds correctly to what you have specified. You have specified that upsmon is to call upssched-script _directly_. This means that the argument to

those mails list are from last century but i give it a try ! created : https://github.com/networkupstools/nut/issues/563 Hello all, Trying to run an EATON 850pro via USB on a Debian Stretch Stable. I have letsencrypt certificate installed and working. When trying to manage the EATON device, i got: upsmon Can not initialize SSL context When 850pro is connected via USB, i can: lsusb Bus 009

Hi everyone, Here I am with my second attempt to persuade upssched to do things; for some reasons it just won't! Or if it runs, it never runs the script. OK, the story first: 2.0.3 (conveniently comes as RPMs by default on FC6) running on FC6; APC Smart-UPS 750 via serial connection all working fine. Here are the main files: /etc/sysconfig/ups SERVER=yes MODEL=apcsmart DEVICE=/dev/ttyS0

Hi all I?m not sure if this is the right place to post but I?m at wits end. So here we go. Running opensuse 11 with two ups that can be seen via web interface and post messages on the console. My issue lies in trying to get the upssched and upsmon to work correctly. Currently I have the exec flags denoted in the upsmon and ?NOTIFYCMD /usr/sbin/upssched? is specified as the NOTIFYCMD flag as

On 9/16/08 3:35 PM, "Arjen de Korte" <nut+users at de-korte.org> wrote: > Citeren tarbeite <tarbeite at fit.edu>: > >> Running opensuse 11 with two ups that can be seen via web interface and post >> messages on the console. > > Please post the contents of /etc/ups/upssched.conf here. Also make > sure that the directory mentioned in PIPEFN and

Was /etc/nut/upssched-cmd automatically installed? I don't have it on my raspberry pi. :-( On 2019-04-03 1:54 p.m., Mike wrote: > I figured this out and it is working now.  This fix seems strange to me > and is possibly a bug.  I'm sharing in case it might help others. > > I had to uncomment all of the NOTIFYFLAG statements whether I was > changing them or not. 

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. > The patch runs successfully on my opensuse 13.2 box, and solves my problem. In upssched.conf I now have declarations such as > > ? ?AT SIGUSR1 * CANCEL-TIMER

This note describes a heartbeat technique for validating the integrity of a NUT installation. Introduction ------------ A NUT configuration may run for months with little or no output to a system administrator to assure that the combined processes are running correctly. The technique described in this note verifies that the ups driver, upsd, upsmon, upssched and upssched-cmd components are

ok, this function really worked? i have a linux Fedora 20 system, i install from rpm in version 2.6.2 and i this function not execute. Then i delete the rpm packet and all configuration files and compile latest stable 2.7.2 version with usb driver. ok, i first load ups driver: * /usr/local/ups/sbin/upsdrvctl -u root start* next i started */usr/local/ups/sbin/upsd* and next*

Hi, I cant seem to get my upssched to get called by upsmon. Upsmon -c fsd just shuts down without the message I set or the one in upssched-cmd /etc/ups/upsmon.conf: MONITOR ups6 at localhost 1 <user> <pass> master MONITOR ups8 at localhost 1 <user> <pass> master SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /usr/sbin/upssched NOTIFYMSG

MASTER SYSTEM nut.conf MODE=netserver ups.conf [TOPAPC] driver = usbhid-ups port = auto pollonly serial = "IS1309002707" desc = "TOPAPC" [MIDAPC] driver = usbhid-ups port = auto pollonly serial = "IS1309001233" desc = "MIDAPC" [BOTAPC] driver = usbhid-ups port = auto