If you look closer at: > pi@nutpi:~ $ sudo ls -alt /home/nutmon > total 32 > -rw------- 1 nutmon nutmon 172 Jan 26 12:32 .bash_history > drwxrwx--- 2 nutmon nutmon 4096 Jan 26 12:32 upssched
there is a d in the first position of the upssched permissions showing this is a directory. This is the directory location for PIPEFN and LOCKFN as defined in upssched-cmd PIPEFN /home/nutmon/upssched/upssched.pipe LOCKFN /home/nutmon/upssched/upssched.lock You are correct there are no EXECs on the relevant NOTIFYFLAGs. When I get home I'll add EXEC to the lines, test and update the thread. On Tue, Jan 28, 2020 at 7:00 AM <[email protected]> wrote: > Send Nut-upsuser mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Nut-upsuser digest..." > > > Today's Topics: > > 1. Re: Timer doesn't appear to start (Roger Price) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 28 Jan 2020 10:14:42 +0100 (CET) > From: Roger Price <[email protected]> > To: nut-upsuser Mailing List <[email protected]> > Subject: Re: [Nut-upsuser] Timer doesn't appear to start > Message-ID: <alpine.LSU.2.20.2001280959120.5507@titan> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > On Mon, 27 Jan 2020, Greg Treantos wrote: > > > root@nutpi:/etc/nut# ps -elf | grep -E '[n]ut|ups[dms]' > > 4 S avahi 246 1 0 80 0 - 1472 poll_s Jan26 ? > 00:00:31 avahi-daemon: running [nutpi.local] > > 1 S nut 451 1 0 80 0 - 678 poll_s Jan26 ? > 00:03:41 /lib/nut/upscode2 -a deltec-PRA1500 > > 1 S nut 454 1 0 80 0 - 1173 poll_s Jan26 ? > 00:00:28 /lib/nut/upsd > > 1 S root 460 1 0 80 0 - 1136 pipe_w Jan26 ? > 00:00:00 /lib/nut/upsmon > > 5 S nutmon 461 460 0 80 0 - 1714 hrtime Jan26 ? > 00:00:10 /lib/nut/upsmon > > The last line shows that the instance of upsmon which should call upssched > is > running as nutmon. Good. > > > [root at donner nut]# grep ^[^#] upsmon.conf > > RUN_AS_USER nutmon > > MONITOR deltec-PRA1500 at localhost 1 nutmon ******** master > > MINSUPPLIES 1 > > SHUTDOWNCMD "/sbin/shutdown -h +0" > > NOTIFYCMD /sbin/upssched > > The last line shows that upsmon expects upssched to be in /sbin. > > > pi@nutpi:~ $ sudo ls -alt /home/nutmon > > total 32 > > -rw------- 1 nutmon nutmon 172 Jan 26 12:32 .bash_history > > drwxrwx--- 2 nutmon nutmon 4096 Jan 26 12:32 upssched > > But this shows that upssched is located in directory /home/nutmon. Is > this the > problem? > > What NOTIFYFLAG declarations with the EXEC option do you have in > upsmon.conf ? > If the declarations > > NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC > NOTIFYFLAG LOWBATT SYSLOG+WALL+EXEC > > are missing, that could also be a problem. > > Roger > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Nut-upsuser mailing list > [email protected] > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser > > ------------------------------ > > End of Nut-upsuser Digest, Vol 175, Issue 35 > ******************************************** > -- Greg http://www.linkedin.com/in/gregtreantos
_______________________________________________ Nut-upsuser mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
