similar to: Is a timer a file?

On Sat, 4 Jun 2016, Charles Lepple wrote: > On Jun 3, 2016, at 6:48 AM, Roger Price <roger at rogerprice.org> wrote: >> ... the timer. I don't see it in /var/lib/ups where the locate tool >> finds upsd.pid, and I don't see it in /run or /var/run where I see >> upsmon.pid. >> > ... it seems that the timers are only stored in memory. See >

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

Hi Roger, reviving this discussion, since we have a Github ticket for 2.7.5: https://github.com/networkupstools/nut/issues/293 2016-06-05 12:34 GMT+02:00 Roger Price <roger at rogerprice.org>: > On Sat, 4 Jun 2016, Charles Lepple wrote: > > On Jun 3, 2016, at 6:48 AM, Roger Price <roger at rogerprice.org> wrote: >> >>> ... the timer. I don't see it in

Hello, I'm using nut with my MG Ellipse on serial port. No problem since one year. Two days ago, I wanted to add a phone alert through my asterisk box when power is down. Since then, upssched doesn't make his job anymore. here is the "syslog" I get when the power cord is unplugged : > > May 9 11:39:34 serveur upsmon[6411]: UPS ellipse@localhost on battery > May 9

Hi Roger, I get: Apr 27 20:50:05 unifi upsmon[1022]: UPS ups on batteryApr 27 20:50:05 unifi upssched[2688]: Timer daemon startedApr 27 20:50:06 unifi upssched[2688]: New timer: onbatt (20 seconds)Apr 27 20:50:26 unifi upssched[2688]: Event: onbattApr 27 20:50:26 unifi upssched[2688]: exec_cmd(/sbin/upssched-cmd.sh onbatt) returned 126Apr 27 20:50:41 unifi upssched[2688]: Timer queue empty,

On Jun 3, 2016, at 6:48 AM, Roger Price <roger at rogerprice.org> wrote: > > Hi, I'm trying to get a better understanding of what a timer is, so I added the following line to upssched.conf > > # Debug - turn on long-running timer to find out where upssched puts it > AT ONBATT * START-TIMER where-am-I 1000 > > I can then start this timer by pulling the power cord

Roger, I did and it didnt work. Hence why I was trying to run just the shell script manually. I am not sure if this works though with the timer defined in it? Cheers, James Date: Mon, 27 Apr 2015 15:03:44 +0200 From: roger at rogerprice.org To: nut-upsuser at lists.alioth.debian.org Subject: Re: [Nut-upsuser] upssched setup On Mon, 27 Apr 2015, James Hammond wrote: > I am unable to get

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

On Fri, 9 Jun 2017, Robbie van der Walle wrote: > ... and also still open is the notification on the Mac. If notify-send is available on the Mac, then perhaps this will work: In upsmon.conf on the Mac you need NOTIFYCMD /usr/sbin/upssched (or wherever this goes on a Mac) NOTIFYFLAG ONBATT SYSLOG+EXEC In upssched.conf you need CMDSCRIPT /usr/sbin/upssched-cmd (or wherever this

Hi, I am unable to get upssched working correctly as my UPS calls low battery too late and there is no way to change it. I am running Nut 2.7.3 on Ubuntu 14.04 I have made this script, called /sbin/upssched-cmd.sh #!/bin/sh case $1 in onbatt) /sbin/upsmon -c fsd;; *) echo "shutdown implemented";; esac I am trying to run the script manually to break down my issues. All that

Bonjour je n?arrive pas ? configurer convenablement NUT pour qu?il m?adresse des SMS en cas de coupure de courant. C?est important pour moi car dans ma maison les coupures sont tr?s fr?quentes. Voici ma configuration : ****************************************************************** 1/ dans /etc/nut/upsmon.conf MONITOR eaton at localhost 1 admin motdepasse master MINSUPPLIES 1 SHUTDOWNCMD

I would like to add a sentence to the man page for upssched.conf. After the sentence "Note that any AT that matches both the notifytype and the upsname for the current event will be used." I propose adding the sentence "If more than one AT matches the notifytype and upsname, the AT declarations are executed in the order in which they appear in upssched.conf. This is the

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

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

Hi! Some systems I have take some time to shut down, so I would like them to shut down if the UPS have been on battery for 2 minutes. Internet has told me that SHUTDOWNCMD ?/sbin/shutdown -h +0? in /etc/nut/upsmon.conf will execute when the UPS is both OB (on battery) and LB (Low battery). Like in wiki.ipfire.org - Detailed NUT Configuration<https://wiki.ipfire.org/addons/nut/detailed>

On January 11, 2020 3:42:15 PM GMT+02:00, Roger Price <roger at rogerprice.org> wrote: >On Sat, 11 Jan 2020, Georgi D. Sotirov wrote: > >> Jan 11 11:49:15 sotirov-bg upsmon[2677]: UPS mgeups at localhost on >battery >> Jan 11 11:49:15 sotirov-bg upssched[29746]: Executing command: >ups-on-battery >> Jan 11 11:49:15 sotirov-bg upssched-cmd: Unrecognized command:

upsmon.conf on server:  https://pastebin.com/z4CrUTxb nut.conf on server:  https://pastebin.com/540ShZH7 Permissions for /etc/nut:  https://hastebin.com/qecolodapi.diff On the Synology (I didn’t edit any of these files): ups.conf:  https://hastebin.com/dedereqizi.shell upsd.conf:  https://hastebin.com/pupeseweda.css upsd.users:  https://hastebin.com/ocenamecex.cs I don’t think I am able to run

Roger, I get 4.3.8(1)-release There was good reason, BTW, for the script to NOT fine the journal script on my machine. I had not downloaded it yet. On 7/14/2019 9:06 AM, Roger Price wrote: > On Sun, 14 Jul 2019, David White wrote: > >> ... I saw nothing that looked like a problem with the report save the >> sections <scriptname> "Cannot access <scriptname>.

On Mon, 10 Aug 2020, Todd Benivegna wrote: > synoups: https://hastebin.com/xexafofiha.bash Wow! What a mess. It looks as if Synology wanted to write their own "NUT", but decided it would be easier to put their ideas in a script when they saw they could use upssched.conf to call it. NUT intends such a script for timer management. Synology use it for general system management.

Hi all, I've not been able to find the answer to my timer problem in the faq or the archives. (or google) Basically, I can't get timers to fire. They fire ignoring the timer value, as if the timer was set to 0. I'm using the OpenFiler distribution, patched to the latest and greatest. upsmon 2.2.2 When I pull the power plug, I see the text "Im In Battery" instantly, instead