similar to: 3phase progress?

The attached patch is a first stab at adding 3phase support to upsstats/upsimage. I got a little carried away, so bare with me. This patch adds 3phase awareness to upsstats/upsimage and the template files, and in additional to the obvious 3phase variables: - upsstats: * Adds IF/ELSE-awareness, and since the parser logic is rather limited this means that we now have IF, ELSE IF etc since all

Hi all! I propose to replace the variables output.voltage.target.line and output.voltage.target.battery with the variable output.voltage.nominal. The reasons for doing it: * Unify naming, the term "nominal" is used both in NUT and by UPS makers for this. * Very few devices (none that I have seen) have a nominal output voltage that differs when on battery/mains. * A single

Hi all! The following files emits warnings when compiled with gcc 4.0: al175.c bcmxcp_ser.c belkinunv.c cyberpower.c everups.c powercom.c solis.c All warnings seem to be of this variety: everups.c:38: warning: pointer targets in passing argument 2 of 'ser_get_char' differ in signedness I suggest that those who fiddles with those drivers fixes the warnings and verifies that it works

Hi! We''ve started to poke and prod at Lustre 1.6.4.1, and it seems to mostly work (we haven''t had it OOPS on us yet like the earlier 1.6-versions did). However, we had this weird incident where an active client (it was copying 4GB files and running ls at the time) got evicted by the MDS and all OST''s. After a while logs indicate that it did recover the connection

Hi all! I'm wondering if there's anyone doing any hacking on the snmp-ups driver at the moment. I've started looking at implementing 3phase-support, and this uncovered some rather unpleasant stuff in the snmp-ups driver that I really need to fix in order to get things sane. Those of you that's allergic to SNMP might want to stop reading now, this is rather icky ;)

Hi, just wanted to confirm that Fiskars UPS 9000 series (aka Powerware Plus 500 series) with optional UPS Information Unit works fine with upscode2 driver. Tested on Fiskars 9200 (20kVA/400V/3ph). Regards, -- Sebastian Zagrodzki Dzia? Sieciowy ICM, Uniwersytet Warszawski s.zagrodzki at net.icm.edu.pl (+48-22) 5520527, 8268009, fax. 8284195 http://www.net.icm.edu.pl/

Can somebody please explain why values are 0-prepended in almost every driver? Since it's done almost everywhere I suspect it's due to some old policy. In theory this might have been a good idea given the assumption that applications are forced to parse the values before presenting them. However, since this isn't done even within NUT I don't see any real reason for doing

I have heard rumors to the affect that there will be a sparc release of lustre incorporating zfs. If this is true does anyone know how I can get a copy, beta test, or sign up for the effort.

Hi! Can someone with CVS write access please remove generated files from the CVS tree? The ones currently on my annoyance-list are: Makefile data/html/Makefile Also, the following files (+more, I only compile a subset of the drivers) should be added to .cvsignore in the corresponding directories (they're all generated): config.log config.status clients/Makefile clients/upsimage.cgi

Hi, I would like to know what TCP/UDP ports should i keep open in my firewall policies on my MGS server such that I can have my MGS server fire-walled. Also if in a event of loss of MGT would it be possible to recreate the MGT without loosing data or bringing the filesystem down (i.e. by using cached information from MDT''s and OST''s) Thanks Anand

2006/1/27, Peter Selinger <selinger@mathstat.dal.ca>: > > ... > battery.mfr.date, which is probably the more accurate interpretation. > > I think the naming should be changed to propose both: - battery.date.mfr: Battery manufacturing date - battery.date.change: Battery change date Any comments? Arnaud -------------- next part -------------- An HTML attachment was scrubbed...

Hi, We have seen a huge performance drop in 1.6.3, due to the checksum being enabled by default. I looked at the algorithm being used, and it is actually a CRC32, which is a very strong algorithm for detecting all sorts of problems, such as single bit errors, swapped bytes, and missing bytes. I''ve been experimenting with using a simple XOR algorithm. I''ve been able to recover

fellows, I'm working on integrating the preliminary HAL support, and thought a bit about the default configure values below: --with-snmp build and install SNMP drivers (no) --with-usb build and install USB drivers (no) [ --with-hal build and install HAL support (no) ] I wonder if some auto detection magic (if the requirement is present enable the

Hi fellows, As the NUT-NG draft will take me more time than I currently have (I found myself too optimistic since I got a baby ;-), below is the beginning of an answer to the "Common Power Management with UPS support" problem... First, NUT is pure userspace code, for portability issue, and will remain. USB is through libusb, snmp through net-snmp and serial through standard read/write.

Hi again! Same setup as before (Lustre 1.6.2 + 2.6.18 kernel). This time things suddenly started to be very slow (as in periodically stalling), and we found a bunch of llog_ LustreErrors on the MDS. Some time later stuff had automagically recovered and is back to normal speed. Any idea on the meaning/cause of these errors? What are the seriousness of "LustreError" errors in

Attached is a patch to be applied with GNU patch -p0, notice that configure needs to be regenerated. The patch addresses the following annoyances: * On AIX there is a signal called SIGDANGER which is sent to all processes when the machine runs low on virtual memory. This patch makes sure that this signal is ignored, because the default on older AIX releases is to kill the running process

Hi, Am 13.02.2012 um 18:58 schrieb Arnaud Quette: > 2012/2/6 thomas schorpp <thomas.schorpp at googlemail.com>: >> Hi, > > Hi Thomas, > >> I want the driver report the battery status from ABM charging controllers >> -patch attached- : > > For now, I've tracked your patch here: >

some notes: - for this kind of discussion, please cc upsdev list (I've added it), - I've fwded the full thread to upsdev, - this subject is part of what I call NUT-NG (next gen.), aka nut 3.0... - I'll study in depth the thread this week end, and complete with my thoughts, - thanks to Stan to have put us all in touch Arnaud 2006/3/10, Stanislav Brabec <sbrabec@suse.cz>: >

2012/2/6 thomas schorpp <thomas.schorpp at googlemail.com>: > Hi, Hi Thomas, > I want the driver report the battery status from ABM charging controllers > -patch attached- : thanks for your patch. since it introduces a new variable (battery.status.abm), I prefer to step back and think to something useful more widely. thus, I'm thinking about a generic

The 2.1.1p3 release of portable OpenSSH has been uploaded to the OpenBSD ftp master site. In a few hours it will be available from one of the many mirrors listed at: http://www.openssh.com/portable.html This release fixes several bugs reported since the previous release and extends portability to NeXT and Reliant Unix. As usual, the OpenBSD team has been hard at work further polishing and