search for: retrrns

...upsmon instance is already running! Usually it should not be running during OS shutdown, which is when checking POWERDOWNFLAG makes most sense. UPS: foo at localhost (primary) (power value 1) Using power down flag file /etc/killpower Power down flag is not set as the man page says "retrrns 0 or 1" and this is replacing if [ -f /etc/killpower ]; then upsmon startup: Network UPS Tools upsmon 2.8.0.1 kill: No such process UPS: foo at localhost (primary) (power value 1) Using power down flag file /etc/killpower again, all knowable statically from config. upsd: Netw...

...upsmon instance is already running! Usually it should not be running during OS shutdown, which is when checking POWERDOWNFLAG makes most sense. UPS: foo at localhost (primary) (power value 1) Using power down flag file /etc/killpower Power down flag is not set as the man page says "retrrns 0 or 1" and this is replacing if [ -f /etc/killpower ]; then upsmon startup: Network UPS Tools upsmon 2.8.0.1 kill: No such process UPS: foo at localhost (primary) (power value 1) Using power down flag file /etc/killpower again, all knowable statically from config. upsd: Netw...

Hello all, During discussion of https://github.com/networkupstools/nut/issues/1782 me and Greg uncovered a diametral difference of opinion about the verbosity of NUT programs in general, and of `upsmon -K` (checking for POWERDOWNFLAG during shutdown integration) in particular. To me as a sysadmin type often (in the past at least) having to troubleshoot the tails and ends of systems'

Hello all, During discussion of https://github.com/networkupstools/nut/issues/1782 me and Greg uncovered a diametral difference of opinion about the verbosity of NUT programs in general, and of `upsmon -K` (checking for POWERDOWNFLAG during shutdown integration) in particular. To me as a sysadmin type often (in the past at least) having to troubleshoot the tails and ends of systems'