similar to: multiple machines

Thanks to the great help here, I now have a UPS spitting out something resembling a report descriptor. So since I seem destined to have to create a new USB HID subdriver, I figured I'd get started on the path. I followed all of the directions on the web....I used the script to generate the usbhid subdriver, feeding it the output of the usbhid-ups driver from reading my UPS. All that worked

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! Has anyone gotten it working at all with Linux :) I picked one up for thiry bucks and would love to monitor it! Liz - -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFD/5fEIACpLcG4dhwRAmeCAJ9+8FGXqKoOlZdkw/KFXb9n0PEemwCdHaoD NVnv7JjmBAjNsExK6WzAdnA= =pcPX - -----END PGP

Den 14-03-2014 21:29, Rob Groner skrev: > It works pretty good after that. However, if I'm going to tailor > my hid2nut table, it would really help if there was some master list > of all the paths (input.voltage, battery.temperature, etc) NUT supports, > instead of having to dig through different driver files to see what's available. Is there some list? How about

I've recently moved from installing NUT from source to installing NUT from the FreeBSD package (FreeBSD 9.1). One would think that I might have learned not to change anything, but I made the change. And here is my tale of woe..... My first question is: is it possible to simulate a "UPS is on battery" state? Some background: UPS comm port is connected to and monitored by

Thanks to Olli, I can now talk to my PW9125 via SNMP: > upsc cscfups001@localhost ambient.temperature: 031.0 battery.charge: 090.0 battery.runtime: 2640.0 battery.voltage: 055.5 driver.name: snmp-ups driver.parameter.mibs: pw driver.parameter.port: cscfups001.cs.uwaterloo.ca driver.version: 2.1.0 driver.version.internal: 0.41 input.frequency: 060.0 input.voltage: 120.0 output.current: 020.0

I'm trying to set up nut with a MGE UPS equiupped with a network management card, but encountered a problem. UPS: MGE Pulsar M 3000 Network Management card (installed in the UPS): 66102 (2006 edition) Operating system: FreeBSD Nut port version: 2.0.5 Nut driver: snmp-ups According to MGE in Norway this card is supported by nut, but only the old version of the card (66244) is listed on

I'm access nut online via localhost. But I have the following problems. When I click on Statistics I get cannot open /etc/hosts.conf. When I click on settings I get: Error: Can't open upsset.conf to verify security settings. Refusing to start until this is fixed. I have .htaccess in cgi-bin with the following: <Files upsset.cgi> deny from all allow from 127.0.0.1 </Files>

With automake, we collectively need to check to see if 'make distcheck' still works after adding or removing files. Basically, nothing will make its way into the NUT distribution tarball unless it is somehow mentioned in one of the Makefile.am files. See the packaging/RedHat directory for an example. Niels, thank you for spotting the extra nut.spec file in SVN; however, it needs to be

Great, thanks! Two questions: * what is a domain literal? Is this something like 192.168.0.1? In this case, the '[]' are probably unnecessary. * are you sure you want to use fprintf(stderr, ...) in a library? This doesn't seem like a good idea to me. Wouldn't it be more consistent to extend upscli_errlist[] ? -- Peter Arjen de Korte wrote: > > Author:

> Author: nba-guest > Date: Mon Apr 24 20:45:39 2006 > New Revision: 414 > > Modified: > trunk/CHANGES > trunk/drivers/cpsups.c > Log: > Fix C++ style declarations between statements > > Modified: trunk/CHANGES Niels, What is the reason for 'fixing' this? Constructions like these are used in many locations throughout the sources (not only in the

I've got persistent trouble getting nut to work, though I think I've done everything by the book (the Debian specific readme included). I've tracked it down to upsd not working as it should: it just won't keep going. :( I.e. checking the process list (or using its reload command) shows that there just isn't a upsd process, at all. Starting upsd with a few -D's for

Hi developers, the current setup when doing a make (even a make -s) is very noisy, and makes it very easy to miss warnings from gcc. I would like to add a --slient option to libtool. How do the rest of you feel about that? /Niels -- Niels Baggesen - @home - ?rhus - Denmark - nba@users.sourceforge.net The purpose of computing is insight, not numbers --- R W Hamming

I've been looking over the documentation and several installation guides for NUT, and I'm starting to get a little bit of a feel for what it is. But I'm still not clear whether what I'd *like* to accomplish is actually practical using NUT. Perhaps someone here can tell me if they've done something similar, or if I'm way off base. I would like to set up a Linux host as a

An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20090120/ffb91e55/attachment.htm

I've used nut for simple configurations before but now one has grown to a more complex setup and can't seem to find any info online. I would like to have single central nut master monitor a bank of UPSs for a whole rack of servers with redundant PSUs. So UPS A1 ---> Server group A PSU 1 UPS A2 ---> Server group A PSU 2 UPS B1 ---> Server group B PSU 1 UPS B2 ---> Server

Hi fellows, are there any policy on character-encoding in this project? The upscode2 driver did originally contain some nordic letters encoded in latin-1 (?, ?), but these have now transformed into garbage. I would like to restore these, but in what encoding? UTF-8? /Niels -- Niels Baggesen - @home - ?rhus - Denmark - nba@users.sourceforge.net The purpose of computing is insight, not numbers

> Right, I forgot to mention that the explore mode is not meant to send data to upsd - it just generates debug output. And it is written in the man page... that I do had read! > There are a few extra variables that might be read/write, but I don't see the usual ones that translate into commands (such as UPS.BatterySystem.Battery.Test or UPS.PowerSummary.DelayBeforeShutdown). > >

I almost had nut_2.0.5-3_i386.deb (from http://packages.debian.org/unstable/admin/nut - installed via dpkg, not via repository) working: * problems with getting it to come up during boot * monitoring via knutclient was OK * shutdown on low battery worked adequately, if not quite as described) and newhidups suddenly stopped talking to my Belkin F6C550-AVR . It's only been in use for a

Hi, I want to use nut-cgi from a centralized machine. There are two firewalls which run upsmon. upsmon connected to the real upsd which run two machines behind the firewall. So upsmon is using LAN for communicating to upsd. First problem: I can't connect to upsmon with upsstats.cgi because upsmon not listen on TCP port. Second problem: How can I check more upsd with upsmon? All upsd are

On Oct 14, 2014, at 12:12 PM, Michael Stinaff <mstinaff at gmail.com> wrote: > I've used nut for simple configurations before but now one has grown to a more complex setup and can't seem to find any info online. > > I would like to have single central nut master monitor a bank of UPSs for a whole rack of servers with redundant PSUs. > > So > UPS A1 --->