I’m wondering if what I have done is good :
# get the source from github on my computer
# autogen.sh
# name=nut
# ./configure --prefix=/ --sysconfdir=/etc/$name --mandir=/usr/share/man
--libdir=/usr/lib --includedir=/usr/include --datadir=/usr/share/$name
--with-statepath=/var/run/nut --with-altpidpath=/var/run/nut
--with-drvpath=/lib/nut --with-pidpath=/var/run/$name
--with-user=$name –with-group=$name --without-ssl
There was an error :
./configure: line 7079: syntax error near unexpected token `CPPUNIT,'
./configure: line 7079: `PKG_CHECK_MODULES(CPPUNIT, cppunit,
have_cppunit=yes, have_cppunit=no)'
I put in commentary the line PKG_CHECK_MODULES(CPPUNIT, cppunit,
have_cppunit=yes, have_cppunit=no) then # make # make installI took the
driver voltronic_ser then from my workstation put it in the server, change the
ups.conf and try it.The command “upscmd –u admin myups shutdown.return” now
work (shutting down server then ups).Unfortunately, when I do “shutdown –h +0”,
the ups is never shut down. After a little research, it appears that the line
“upsmon –K >/dev/null 2>&1” in ups-monitor always return 1 so the line “exec
/etc/init.d/nut-server poweroff” is never execute.I’m ussing upssched in
upsmon.conf, do I need to create the flag with my script before calling the
shutdown –h +0? How (it’s supposed to be set automaticaly)? or maybe I’m
missing something.
Did I do the right thing by getting only the driver from my computer and put it
on the server? Or should I do a package of the whole nut (binary, conf etc...)
Best regards,
From: [email protected]
Sent: Monday, July 29, 2013 1:34 AM
To: James HORLEY
Subject: Re: [Nut-upsuser] infosec e4
You could try voltronic driver
https://github.com/networkupstools/nut/tree/voltronic-driver
/dan
2013/7/29 James HORLEY <[email protected]>
Hi,
Sorry for my poor english but it isn’t my native language.
I’m testing an infosec E4 with nut-2.6.4-2.3 on Proxmox ve 3.0 (based on
debian wheezy). The drivers that match this ups, is blazer_usb.
Btw, I have try nut-2.6.5 with unstable repository from wheezy, but it still
doesn’t fully work.
I can shutdown my computer when battery is low, but unfortunately I can’t
shutdown ups.
Like said on the man blazer :
“Some UPS commands aren’t supported by all models. In most cases, the
driver will send a message to the system log when the user tries to execute an
unsupported command”
I’m wondering if there’s a way I can post some data to help make this ups more
compatible with NUT.
There’s a software advised by the constructor that work on linux
(http://www.power-software-download.com/viewpower.html), unfortunately it’s
heavy (tomcat and java) and I don’t find it as flexible as NUT.
Best regards,
_______________________________________________
Nut-upsuser mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
_______________________________________________
Nut-upsuser mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
