similar to: Asking hard questions about the NUT architecture

Scenario 1: Package-centric Have the .deb package for NUT install a single-user/single-UPS configuration, with the .deb asking for the UPS type and dispatching on that to set up ups.conf for the correct driver. Package installation could even create a nut user and group, so there wouldn't even be a security compromise. I don't know how to do the equivalent with RPM, because RPM

On Jul 9, 2014, at 6:31 AM, Eric S. Raymond <esr at thyrsus.com> wrote: > What I'd like to do is this: confer in real-time, perhaps via IRC, > with someone who knows this process. Ask about every step (thought > processes and diagnostics). *Write them down* and turn this into a > document on how to qualify and support a new device. Happy to help, but scheduling something

I think the time for me to get involved in NUT documentation has come again. Late last week I had to buy a UPS under time pressure. The Eaton unit that thus project gifted me with in 2006(?) died during a severe thunderstorm watch, so it was off to MicroCenter to get a replacement pronto. I wound up buying an APC BN700MC. It was what they had in the performance range I needed. The removable

I just bought a pair of Belkin USB UPSes -- F6C1200-UNV and F6C550-AVR -- and installed the latest version of nut under Ubuntu 7.04. I'm using the F6C1200-UNV. My system does see the device; dmesg says [ 82.718428] usb 2-2: new low speed USB device using ohci_hcd and address 2 [ 82.941189] usb 2-2: configuration #1 chosen from 1 choice [ 83.036825] usbcore: registered new driver

I just bought a pair of Belkin USB UPSes -- F6C1200-UNV and F6C550-AVR -- and installed the latest version of nut under Ubuntu 7.04. I'm using the F6C1200-UNV. My system does see the device; dmesg says [ 82.718428] usb 2-2: new low speed USB device using ohci_hcd and address 2 [ 82.941189] usb 2-2: configuration #1 chosen from 1 choice [ 83.036825] usbcore: registered new driver

Hi all, Currently, the "megatec" driver only supports UPSes which have a serial (RS232) interface. However, I'm under the impression that most of the models that speak the megatec protocol, and have an USB interface, just have a standard serial-to-USB converter inside. This being the case, there should be a "/dev/ttyUSBx" device which the megatec driver could use just as

Hi all, Currently, the "megatec" driver only supports UPSes which have a serial (RS232) interface. However, I'm under the impression that most of the models that speak the megatec protocol, and have an USB interface, just have a standard serial-to-USB converter inside. This being the case, there should be a "/dev/ttyUSBx" device which the megatec driver could use just as

Hi Ted there was a drift from the initial topic. worth a new thread! 2014-07-27 9:13 GMT+02:00 Ted Mittelstaedt <tedm at mittelstaedt.us>: > On 7/26/2014 12:18 PM, Arnaud Quette wrote: > >> Hi Eric, >> >> sorry for the lag, summer time... >> >> I'm first seconding Charles comments >> >> 2014-07-09 12:31 GMT+02:00 Eric S. Raymond <esr

Hi, I'd like to know your opinion for bug http://bugzilla.redhat.com/show_bug.cgi?id=544121 Recently serial connected UPSes stopped working because ModemManager steals tty devices (it tries to open every tty device to check if there is modem sitting there), this means device is blocked for about 10 seconds. This prevents nut daemon to start. I've reassigned bug against ModemManager

On 11/9/2013 5:24 AM, Jim Klimov wrote: > Hello all, > > I am trying to set up my brother's UPS (remotely over internet) > on an OpenIndiana-based storage box. According to him, the UPS is > probably an Ippon Back Power Pro 600 dated around 2003 (battery > recently replaced), and it has an USB connection. > > Sorry for a relatively long post with a log of my successes

Got the: git clone git://github.com/networkupstools/nut.git To work. Had to all so do this: apt-get install autoconf apt-get install libtool Did put driver = usbhid-ups in the /etc/nut/ups.conf file like you said. Here is what I got for it all: root at odroid-u2:~/nut# ./autogen.sh Calling autoreconf... libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'. libtoolize: copying

On 7/9/2014 6:51 AM, Charles Lepple wrote: > On Jul 9, 2014, at 6:31 AM, Eric S. Raymond<esr at thyrsus.com> wrote: > >> What I'd like to do is this: confer in real-time, perhaps via IRC, >> with someone who knows this process. Ask about every step >> (thought processes and diagnostics). *Write them down* and turn >> this into a document on how to qualify

Hi Mario, Mario Cassani wrote: > Hallo Arnaud, > some months ago I bought an SBS GC400 UPS. > I came with a kit RS232 + UPSmart CDROM that works only with RedHat 7.0-7.3. > As I use Debian I tried alien with no success. > > Can you please provide me with any hint to understand if my UPS can be managed by NUT? > Can a driver be written, knowing how the cable

Hi Eric, sorry for the lag, summer time... I'm first seconding Charles comments 2014-07-09 12:31 GMT+02:00 Eric S. Raymond <esr at thyrsus.com>: > I think the time for me to get involved in NUT documentation has come > again. > welcome back > Late last week I had to buy a UPS under time pressure. The Eaton unit > that thus project gifted me with in 2006(?) died

Hi, it'd be great if you could update the documentation on the website that some models of the Belkin -UNV series will only work with the megatec(_usb) drivers. I wasted a lot of time on trying to get it to work with the wrong drivers, and would like to spare others the pain :-). Thanks, ~David P.S. Some forum post said that the stable megatec drivers don't work 100% with the belkin UPS,

Hi, it'd be great if you could update the documentation on the website that some models of the Belkin -UNV series will only work with the megatec(_usb) drivers. I wasted a lot of time on trying to get it to work with the wrong drivers, and would like to spare others the pain :-). Thanks, ~David P.S. Some forum post said that the stable megatec drivers don't work 100% with the belkin UPS,

Additional question: I noticed on the HP Website that the latest version of "CPQPOWER.MIB" (1.76, dated Sept. 19, 2013) was more recent than the related file (./drivers/compaq-mib.c) in the NUT driver. Is the MIB structure as implemented on the management card perhaps no longer in line with the NUT driver ? The latest MIB file can be downloaded from the following URL:

Carsten, This is a common issue in technology when you have complex products that the majority of consumers of those products do not understand how they operate. If most UPS customers understood the importance of standardization they would have refused to purchase non-standard UPSes and all UPSes would have long ago standardized on a single management protocol. The normal thing is that product

Hello, I've got a setup with NUT, where we've got two UPSes, ups1 and ups2. UPS1 supports our servers, while UPS2 supports our desktop boxes. We monitor both of them via USB on a box now called "upsmon". The interesting point comes here. We monitor both UPSes on the upsmon box, but if UPS2 fails, which supports our desktop boxes, NUT shouldn't initiate a shutdown in

As previously noted, I need to replace a UPS and want to do my product research in public so others can benefit. The information I elicit on this thread will be merged into the UPS-HOWTO. I went to my local computer-equiuipment big-box store, a place called MicroCenter in Ardmore, Pennsylvania. I looked at the range of "UPS" devices they sell and was *completely* confused. Bear in