[Nut-upsuser] Any suggestions why /bin/upssched-cmd isn't getting invoked?

[Roger Price]

On Sat, 29 Apr 2023, Willcox David via Nut-upsuser wrote:

> Content of upsmon.conf: (I probably should have called it something other than “usbhid,” but that’s working for now.)
> 
> > RUN_AS_USER upsmon
> > MONITOR usbhid at localhost 1 upsmon_master <thepassword> master
> > MINSUPPLIES 1
> > SHUTDOWNCMD "/sbin/shutdown -h +0"
> > POLLFREQ 5
> > POLLFREQALERT 5
> > HOSTSYNC 15
> > DEADTIME 15
> > POWERDOWNFLAG /etc/killpower
> > NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC
> > NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC
> > NOTIFYFLAG LOWBATT SYSLOG+WALL+EXEC
> > NOTIFYFLAG REPLBATT SYSLOG+WALL+EXEC
> > RBWARNTIME 43200
> > NOCOMMWARNTIME 300
> > FINALDELAY 5

I don't see the « NOTIFYCMD <path-to>/<file-name> » line in this file which says 
which program is to be invoked when upsmon detects a NOTIFY event flagged as 
EXEC.  Could this be the culprit?

Roger