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: [email protected] 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
_______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
