I am using the usbhid-ups driver with a Belkin UPS.
upsc shows several parameters which I would like to both understand and
probably change. In particular the following part of upsc output:
battery.charge.low: 30
battery.charge.warning: 30
battery.runtime: 120
My questions are:
1) What is the
Hi John
I am using a very similar Belkin UPS with nut 2.2.0 and Centos 5.3.
I can't find my exact model number but I think mine is the 1200va
version similar to yours. I also tried installing the supplied Linux
drivers - but gave up. I also gave up on the serial connection.
But I have got it wo
cript - somehow test whether we are still on battery - and if so
- issue the shut-down immediately.
Out of interest - do you know what the ups parameter:
battery.runtime: 120
Means - and where might it be documented?
Thanks Jon
Richard.
Jon Bendtsen wrote:
On 20/05/2009, at 12.11, Richard Ch
I have read the NUT document /usr/share/doc/nut-2.2.0/docs/shutdown.txt
And in particular the section called "RAID Warning".
In response to this section I have added the two lnes, but haven't yet
tested it:
mdadm --readonly /dev/md0
mdadm --readonly /dev/md1
into /etc/rc.d/init.d/halt
Thus:
-
For various reasons - I have been trying to get my Desktops and/or
servers to shut-down a fixed time after a power fail - or better still a
fixed time - or a low battery whichever comes first.
I note in my upsc:
*> upsc belkinusb*
battery.charge: 100
battery.charge.low: 30
battery.charge.warnin
I am aware of 2 windows nut clients both interestingly called winnut.
One (winnut 2.0.0b) is a service based client based on a port of the but
client code (I think). The other is a GUI client based on (I think
again) on knutclient .
I have corresponded with both authors about a feature reques
Hi all
Is the syntax:
ACL lan 10.0.0.0/255.0.0.0
allowed and correct? Shouldn't it be:
ACL lan 10.0.0.0/8
If both notations are allowed in the same syntax - it is news to me - but then
many things are news to me...:-)
Richard.
Charles Lepple wrote:
> On Dec 21, 2007 11:07 AM, Ricardo Bu
Hi Arjen
I guess you are right that we learned something from running the driver
stand alone - but the debug level didn't seem to add as much verbosity
as it did with other drivers. I have checked on your suggestions:
> A couple of things can be wrong here. The serial port (or the setup) is
> b
Richard Chapman wrote:
Hi Charles.
A quick update on statserial:
Well obviously I did need to install another package - rather
cryptically called statserial...:-)
But unfortunately it didn't help much:
[EMAIL PROTECTED] /]# statserial /dev/ttyS0
statserial: TIOCMGET failed: Invalid arg
Hi Charles - and thanks for your help.
Firstly just to fill you in - I have tried both Serial and USB
connections. I have the USB connection "sort of" working - but only when
I manually set permissions - which need to be manually re-set
occasionally. This is not very satisfactory - and Tomas Sm
I can't really help - but have a similar problem with a different UPS. I
have a Belkin ups with belkinunv driver which claims to support my
model. I get a different error - but essentially the same issue. It just
doesn't seem to get anything back from the UPS on ttyS0. I have checked
the permi
should try launching the serial driver (BelkinUnv) in debug mode to see
if I can find out what the problem is there. If I find anything - I will
also let you know.
Best regards and many thanks.
Richard.
Tomáš Smetana wrote:
On Tue, 27 Nov 2007 16:01:26 +0900
Richard Chapman <[EMAIL PROT
from their RHEL? Did they
replace it with something?
Again thank you both for your help.
Richard.
Tomáš Smetana wrote:
On Mon, 26 Nov 2007 21:36:29 +0900
Richard Chapman <[EMAIL PROTECTED]> wrote:
Hi Arjen
Also for Tomas Smetana of the epel repository
I think we are getting some
the action script - but I'm not sure it will help.
Thanks Arjen (and Tomas).
Richard.
Arjen de Korte wrote:
Richard Chapman wrote:
I have changed the driver in my ups.conf to usbhid-ups, and based on
other literature I have read - I set the port to "auto", but at startup
i
Thanks Arjen
I have changed the driver in my ups.conf to usbhid-ups, and based on
other literature I have read - I set the port to "auto", but at startup
i get the error:
Starting UPS driver controller: Network UPS Tools: 0.28 USB communication
driver 0.28 - core 0.30 (2.2.0-)
No matchin
Hi Arjen
My apologies fro drifting off topic in the other mailing list...:-)
On the bottom of the Belkin UPS unit - is the model number: F6C120auUNV
The "au" is for Australia I think.
"man belkinunv" states that F6C120-UNV is supported - and I assumed that
the "au" would not prevent this.
I plug
Hi Arjen
>
> My apologies fro drifting off topic in the other mailing list...:-)
>
> On the bottom of the Belkin UPS unit - is the model number: F6C120auUNV
> The "au" is for Australia I think.
> "man belkinunv" states that F6C120-UNV is supported - and I assumed
> that the "au" would not prevent
17 matches
Mail list logo