Humberto Möckel
2017-Apr-14 02:22 UTC
[Nut-upsuser] Windows: SHUTDOWNCMD stopped working after Creators Update
Hi all! All was working fine with all my UPSs and Windows 10 machines, NUT will notify events to NOTIFYCMD (which point to a .bat script to show messages) and finally will shutdown the system via SHUTDOWNCMD, that is another .bat file that simply uses shutdown.exe to hibernate the system. Today I upgraded all my machines to the latest Creators Update, and now NOTIFYCMD works as I can see messages, but when a forced shutdown is called via fsd command NUT will shutdown all the processes as usual but it won?t call out the SHUTDOWNCMD batch file. It?s not a problem with the script as I have tested it with other ones, it simply doesn?t call it anymore, so the system will stay on without NUT running. Any ideas? Thanks Gesendet von Mail f?r Windows 10 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170413/d99e57f7/attachment.html>
Humberto Möckel
2017-Apr-14 21:33 UTC
[Nut-upsuser] Windows: SHUTDOWNCMD stopped working after Creators Update
I think it has to do with the split-process model that upsmon uses, am I right? If I start upsmon from a cmd console with admin privileges and then force a shutdown it calls the SHUTDWNCMD bat file correctly. But it doesn?t work anymore when upsmon is run as a Windows Service. Before the Creators Update it did work, maybe they changed something in the privileges System. Any help would be awesome. As a Workaround I?m planning on running the shutdown.exe directly with NOTIFYCMD commands, but it?s a shame that SHUTDOWNCMD isn?t working anymore. Gesendet von Mail f?r Windows 10 Von: Humberto M?ckel Gesendet: Donnerstag, 13. April 2017 23:22 An: nut-upsuser at lists.alioth.debian.org Betreff: Windows: SHUTDOWNCMD stopped working after Creators Update Hi all! All was working fine with all my UPSs and Windows 10 machines, NUT will notify events to NOTIFYCMD (which point to a .bat script to show messages) and finally will shutdown the system via SHUTDOWNCMD, that is another .bat file that simply uses shutdown.exe to hibernate the system. Today I upgraded all my machines to the latest Creators Update, and now NOTIFYCMD works as I can see messages, but when a forced shutdown is called via fsd command NUT will shutdown all the processes as usual but it won?t call out the SHUTDOWNCMD batch file. It?s not a problem with the script as I have tested it with other ones, it simply doesn?t call it anymore, so the system will stay on without NUT running. Any ideas? Thanks Gesendet von Mail f?r Windows 10 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170414/bd02e3f1/attachment.html>
Possibly Parallel Threads
- NOTIFYCMD and SHUTDOWNCMD do not work until Nut is restarted
- How to shutdown macOS / mac OSX from Network UPS Tools client - NUT
- I'm new to NUT in Windows, having problems with blazer_usb doing an UPS shutdown
- How to shutdown macOS / mac OSX from Network UPS Tools client - NUT
- NOTIFYCMD doesn't work from Windows service