upsmon: avoid getting killed due to systemd timeout during lengthy shutdown

[jimklimov]

Follows up from #3003

NOTE: Also checking NUT CI - OBS integration for #1209

[jimklimov]

@ErikDB87 : I hope now the PR is ready for practical testing, for whether I've identified the problem and ways around it correctly :)

[ErikDB87]

@ErikDB87 : I hope now the PR is ready for practical testing, for whether I've identified the problem and ways around it correctly :)

To be certain: you want me to git clone https://github.com/jimklimov/nut -b issue-3003 nut-issue-3003, do the build process and run sudo upsmon -c fsd, correct?

(If so, I'm going to leave the UPS plugged in into the power outlet. If sudo upsmon -c fsd doesn't seem to do anything, I'm just going to reboot my primary Linux device. I'll refrain from trying other commands.)

[jimklimov]

Yes, with the caveat that upsmon -fsd sends a signal to the currently running daemon, so that too should be from the new build. I suppose you can systemctl stop nut-monitor and then from the build area run ./clients/upsmon -DDDDDD & sleep 15; ./clients/upsmon -fsd to only run the new binary for this without installing it (if you're wary to).

[ErikDB87]

Okay, I uninstalled the build I had, cloned after your latest commit, ran the install process and ran sudo upsmon -c fsd (after first erroneously running sudo upsmon -fsd 🙄). The script worked, since the router turned off. The secondary turned off as well. Only the primary didn't...

I also had the impression the router kept being shut down, since restarting it had no effect on networks aooearing, and the device turned out to be off again later (after restarting it earlier, obviously).

Checking capture.txt, it indeed looks like the script was being run over and over again. So something is still off...

See logs here: https://drive.google.com/drive/folders/1D5M7YUbbd3sezB804D-dVm-f_Ofl9mj9?usp=sharing