[Nut-upsuser] NUT Windows port questions

Denis Serov dns-srv at yandex.ru
Thu Jan 5 13:40:43 UTC 2012

Hi Frederic!

Thank you for your answers...

>> 1. It seems that it impossible to use long file names with spaces in 
>> PIPEFN/LOCKFN/NOTIFYCMD/... (like "C:\Program Files (x86)\NUT\sbin
>> \upssched.exe") or I couldn't find the way (error: cannot find "C:
>> \Program "). Environment variables are not supported too (it would be 
>> great to use %ProgramFiles% in the paths).
>> This problem is the reason, why I had to use "C:\NUT\NUT" directory 
>> for pipe & lock. Moreover, to start "upssched.exe" via NOTIFYCMD, I 
>> included "C:\Program Files (x86)\NUT\bin" and "C:\Program Files 
>> (x86)\NUT\sbin" into %PATH% variable.

> Indeed using name with spaces is not obvious and I have recently added a note this in the doc. This is an example of what you need :

> PIPEFN "\"C:\\Program Files\\NUT\\upssched.pipe\""

> Let me know if this solve this point.

I didn't check PIPEFN, but I have some results for NOTIFYCMD:

NOTIFYCMD "\"C:\\Program Files (x86)\\NUT\\notify.cmd\""

Network UPS Tools upsmon 2.6.0-2988:2989M
   0.000000     UPS: mainups at (slave) (power value 1)
   0.000000     Using power down flag file C:\killpower.flag
   0.015600     debug level is '1'
   0.015600     Trying to connect to UPS [mainups at]
   0.031200     Logged into UPS mainups at
   8.135114     UPS mainups at on battery
'C:\Program' is not recognized as an internal or external command, operable program or batch file.

With the best wishes,

More information about the Nut-upsuser mailing list