On Thu, 2012-01-05 at 17:40 +0400, Denis Serov wrote:
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:
Hi Denis,
2012/1/4 Serov Denis dns-...@yandex.ru
Hello NUT Team!
I've got some questions about NUT (Windows port), which I couldn't resolve
by myself.
I have a test environment that contains:
1. NUT network server (OS: Debian 6.0.3, x64, NUT 2.4.3)
2. Linux clients (OS: different, NUT
On Wed, 2012-01-04 at 23:44 +0400, Serov Denis wrote:
Hello NUT Team!
I've got some questions about NUT (Windows port), which I couldn't
resolve by myself.
I have a test environment that contains:
1. NUT network server (OS: Debian 6.0.3, x64, NUT 2.4.3)
2. Linux clients (OS: different,
Hi Arnaud!
Hi Denis,
the Windows port is not yet fully functional, nor as mature as the Unix
versions.
Currently, upssched is not working.
It is indeed sad...
So you can only use the simple scheduling approach:
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
Hello NUT Team! I've got some questions about NUT (Windows port), which I couldn't resolve by myself. I have a test environment that contains:1. NUT network server (OS: Debian 6.0.3, x64, NUT 2.4.3)2. Linux clients (OS: different, NUT 2.4.3, 2.6.1)3. Windows clients (OS: Windows Standard Server
Hello NUT Team!
I've got some questions about NUT (Windows port), which I couldn't resolve
by myself.
I have a test environment that contains:
1. NUT network server (OS: Debian 6.0.3, x64, NUT 2.4.3)
2. Linux clients (OS: different, NUT 2.4.3, 2.6.1)
3. Windows clients (OS: Windows Standard
7 matches
Mail list logo