similar to: Remove generated files from cvs-devel

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! I've been (very) out of the loop for a while, up to the point that I had completely missed that the mailing list has moved. Oh well. However, Kjell Claesson poked at me regarding the 3phase stuff, so I found out that I had missed the recent events. In any case, it seems that the situation is unchanged regarding 3phase support. As some of you remember I made a suggestion for a

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

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 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

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

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 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 ;)

Stanislav Brabec wrote: > Please note that 2.2.2-pre3 installs hald addons by default to / on > openSUSE 11.0 beta 2 x86_64. Not a big problem. Here is a patch, which fixes openSUSE 11.0 beta 2 x86_64: --- m4/nut_check_libhal.m4 +++ m4/nut_check_libhal.m4 @@ -63,7 +63,7 @@ dnl As per HAL spec, ?5 Callouts and ?2 Device Information Files dnl - addon install path: $libdir/hal

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.

I have been trying to get Nut working on a system with Fedora 8 i86_64 installed and an APC Smart-UPS USB. The 2.2.0 rpm does not seem to like the USB on this UPS. I have tried compiling the 2.2.2 version, from source, but am getting warnings. I have tried building it on my i386 system (f8 as well) and I get no warnings also the 2.2.0 works fine on that one with a TrippLite Omni 900 LCD via

This is the patch to include SVN revision level in version number displays. There should be two enclosures; the patch itself and a new source file. common/upsversion.c. upversion.c defines a single function. upsversion(), that returns a version string for display. Some Makefile trickery ensures that this file will be recompiled whenever the project's SVN revision level has changed since it

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/

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: >

I'll test it. I'm a bit confused with cgi-bin. I have made a lot of hosts.conf copies and didn't understand where does upsstats trying to find hosts.conf # ps -aux | grep ups _ups 13934 0.0 0.0 484 920 ?? Ss 5:41PM 0:01.53 /usr/local/bin/riello_ser -a senpro _ups 9171 0.0 0.1 532 1168 ?? Ss 5:41PM 0:00.13 /usr/local/sbin/upsd _ups 16906 0.0 0.1

Hi, To to build an RPM from the nut 2.0.3 source I've corrected the old nut.spec.in file. Please find a copy of the slightly updated spec file attached. The changes are documented at the bottom of the spec file. Regards, Will -------------- next part -------------- # don't know how different I can do this %define majorver 2.0 %define version 2.0.3 %define relver 1 %define nutuser

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, 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

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