Re: [Nut-upsuser] Revive support for HP PowerTrust?

2007-01-02 Thread Charles Lepple
On 1/2/07, Jakob Haufe <[EMAIL PROTECTED]> wrote: Hi everyone. I'm currently looking for a monitoring program for a HP PowerTrust UPS (A2998A) for Linux. It seems that nut supported these UPSs until version 1.4.3. What was the reason for the driver being removed from nut? Are there plans to rei

Re: [Nut-upsuser] SNMP/management front-ends

2007-01-02 Thread Charles Lepple
On 1/2/07, Eric A. Hall <[EMAIL PROTECTED]> wrote: I've been using TrippLite's PowerAlert software with my RM2200XL2U rack system and my APC BackUPS desktop systems. Unfortunately it doesn't work with openSUSE 10.2 (the software has problems with the serial port and UPS interfaces on openSUSE 10.

Re: [Nut-upsuser] Geek Squad UPS Systems

2007-01-02 Thread Charles Lepple
On 1/2/07, Kory Hamzeh <[EMAIL PROTECTED]> wrote: 1. Off hand, do you know the name of the serial device for Com1 on Fedora Core 6.0? Should be /dev/ttyS0. You can also find the names by running 'dmesg|grep ttyS' if your system was recently booted, or (as root) 'cat /proc/tty/driver/serial' -

[Nut-upsuser] RE: Geek Squad UPS Systems

2007-01-02 Thread Daniel Gimpelevich
On Tue, 02 Jan 2007 12:03:29 -0700, Kory Hamzeh wrote: > 1. Off hand, do you know the name of the serial device for Com1 on > Fedora Core 6.0? /dev/ttyS0 ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/m

Re: [Nut-upsuser] Geek Squad UPS Systems

2007-01-02 Thread Peter Selinger
To check if your device's USB interface is supported, try the newhidups driver. You can run this driver (at first) as drivers/newhidups -DD -u root auto If the device is not (yet) supported, then please find out the vendor id and product id of the device; they should be in the debug output from

Re: [Nut-upsuser] Geek Squad UPS Systems

2007-01-02 Thread Arjen de Korte
Kory Hamzeh wrote: > Thanks for the info. I will give it a try. It has both a USB and a > serial port. Eventually, I'd like to use the USB interface instead of > the serial. We have not tested the USB connection, but based on other drivers, this likely is not going to work. Unless the serial-to-U

[Nut-upsuser] SNMP/management front-ends

2007-01-02 Thread Eric A. Hall
Hi, I've been using TrippLite's PowerAlert software with my RM2200XL2U rack system and my APC BackUPS desktop systems. Unfortunately it doesn't work with openSUSE 10.2 (the software has problems with the serial port and UPS interfaces on openSUSE 10.2), so I've been looking at other options. I se

[Nut-upsuser] Revive support for HP PowerTrust?

2007-01-02 Thread Jakob Haufe
Hi everyone. I'm currently looking for a monitoring program for a HP PowerTrust UPS (A2998A) for Linux. It seems that nut supported these UPSs until version 1.4.3. What was the reason for the driver being removed from nut? Are there plans to reintegrate it? I was playing around with the UPS and

RE: [Nut-upsuser] Geek Squad UPS Systems

2007-01-02 Thread Kory Hamzeh
> an easy way to test it is: > > open your serial port to your ups with cu (ie cu -s 2400 -l > /dev/serialdevicename) > > once it is opened, hit (a couple times if needed). if you see a >#2, type in P4, and post back the info it returns. Doug, Thanks for the info. I will give it a try. It ha

Re: [Nut-upsuser] ownership of pid directory

2007-01-02 Thread David Benfell
On Tue, 02 Jan 2007 09:53:46 -0500, Doug Reynolds wrote: > > > I have an answer to your question now (i don't recall if you got an > answer now) since I run freebsd, I finally secure nut on my system. > > my /var/db/nut dir looks like this: > > drwxr-x---2 nutmon nut 512 Jan

Re: [Nut-upsuser] ownership of pid directory

2007-01-02 Thread Doug Reynolds
Hello all, Some time ago, you all were very helpful in getting nut running on an OpenBSD system, using--for what it's worth--a CyberPower 1500AVR. So I finally got my FreeBSD system's UPS, also a CyberPower 1500AVR, within reach of its serial cable and I'm trying to get nut running here. I'm g

Re: [Nut-upsuser] Geek Squad UPS Systems

2007-01-02 Thread Doug Reynolds
Kory Hamzeh wrote: We are interested in using Nut on our Federa 6.0 servers. However, our UPS systems are sold under the name "Geek Squad" (sold through the Best Buy chain of department stores). I'm pretty certain Geek Squad does not manufacture these units and they just rebrand them. Does anyone

Re: [Nut-upsuser] Help with nut 2.0.4, MGE Ellipse 1000 and FreeBSD

2007-01-02 Thread Arjen de Korte
> Alternatively, we could remove the 'static' from > > static unsigned int poll_interval = 2; > > in 'drivers/main.c' and add > > static unsigned int poll_interval; The latter should read extern unsigned int poll_interval; of course (the fingers were quicker than the brain). Best regar

Re: [Nut-upsuser] Help with nut 2.0.4, MGE Ellipse 1000 and FreeBSD

2007-01-02 Thread Arjen de Korte
>> More generally, I'll start a discussion about the driver polling rate >> (2 sec) which was accurate with the dumb and old smart units, but >> which is really too high for recent / verbose units (that also support >> an interrupt / notification mechanism, allowing to lower the polling >> rate, w

Re: [Nut-upsuser] Help with nut 2.0.4, MGE Ellipse 1000 and FreeBSD

2007-01-02 Thread Arnaud Quette
2007/1/2, Arjen de Korte <[EMAIL PROTECTED]>: > bug fixes are definitely welcome for the final 2.0.5... > so don't hesitate to backport theses change. I already did. :-) ok, thanks. I've not yet digged the commit list... > More generally, I'll start a discussion about the driver polling rat

Re: [Nut-upsuser] Help with nut 2.0.4, MGE Ellipse 1000 and FreeBSD

2007-01-02 Thread Arjen de Korte
> bug fixes are definitely welcome for the final 2.0.5... > so don't hesitate to backport theses change. I already did. :-) > More generally, I'll start a discussion about the driver polling rate > (2 sec) which was accurate with the dumb and old smart units, but > which is really too high for r

Re: [Nut-upsuser] Help with nut 2.0.4, MGE Ellipse 1000 and FreeBSD

2007-01-02 Thread Arnaud Quette
happy new year fellows, 2006/12/29, Arjen de Korte <[EMAIL PROTECTED]>: >>> It looks like the connection between driver and upsd is continuously >>> dropping. This could be a driver problem or an upsd problem. Since the >>> driver is not reporting anything out of the ordinary, I suggest to >>>