, 2011-02-15 at 13:16:58 -, Arnaud Quette wrote:
this is not the problem. This code is in the smartmode() function of
apcsmart.c:
http://svn.debian.org/wsvn/nut/trunk/drivers/apcsmart.c
we see the 5 attempts to go to smart mode ('Y' command), but my aim is to
understand why it is failing
, 2011-02-15 at 13:16:58 -, Arnaud Quette wrote:
this is not the problem. This code is in the smartmode() function of
apcsmart.c:
http://svn.debian.org/wsvn/nut/trunk/drivers/apcsmart.c
we see the 5 attempts to go to smart mode ('Y' command), but my aim is to
understand why it is failing
, 2011-02-15 at 13:16:58 -, Arnaud Quette wrote:
this is not the problem. This code is in the smartmode() function of
apcsmart.c:
http://svn.debian.org/wsvn/nut/trunk/drivers/apcsmart.c
we see the 5 attempts to go to smart mode ('Y' command), but my aim is to
understand why it is failing
2011/4/20 Charles Lepple clep...@gmail.com
On Apr 19, 2011, at 10:26 AM, Arnaud Quette wrote:
what still puzzles me is that _upsd._tcp is used as Service Type.
while nut is used as the Service Name.
(instant update) I've just made a quick test with Frédéric, and the nut
name *must
Hi Charles,
2011/4/19 Charles Lepple clep...@gmail.com
On Apr 19, 2011, at 7:44 AM, Arnaud Quette wrote:
Author: aquette
Date: Tue Apr 19 11:43:46 2011
New Revision: 2974
URL: http://trac.networkupstools.org/projects/nut/changeset/2974
...
+void scan_nut_avahi()
+{
+ printf
2011/4/15 Michal Soltys sol...@ziu.info
W dniu 14.04.2011 23:49, Arnaud Quette pisze:
I would more be in favor of finally using the extra param of
instcmd(const char *cmdname, const char *extra)
and mapping these commands onto existing ones. Specific parameters would
then be described
so what if you issue again an upsc powercom?
does it still broke the pipe?
is your issue 100 % reproducible?
my guess, is ATM, that the faulty end-of-line marker in battery.type is
causing parseconf to close prematurely the connexion, while upsd is still
sending data.
which explains why unit
2011/4/18 Virus 753...@bugs.launchpad.net
yes, it 100 % reproducible.
I also managed to reproduce it using dummy-ups (the simulation driver) and
injecting the error on the same variable:
adding a newline (ie \n) results in a broken pipe on upsc side.
i am ready to test svn version.
ok,
2011/4/18 Virus 753...@bugs.launchpad.net
It`s working great! Many thanks!
excellent, thanks for the feedback.
I've just committed it upstream (r2972)
the changeset will be available on the NUT Trac mirror (just give it some
minutes to sync):
so what if you issue again an upsc powercom?
does it still broke the pipe?
is your issue 100 % reproducible?
my guess, is ATM, that the faulty end-of-line marker in battery.type is
causing parseconf to close prematurely the connexion, while upsd is still
sending data.
which explains why unit
2011/4/18 Virus 753...@bugs.launchpad.net
yes, it 100 % reproducible.
I also managed to reproduce it using dummy-ups (the simulation driver) and
injecting the error on the same variable:
adding a newline (ie \n) results in a broken pipe on upsc side.
i am ready to test svn version.
ok,
2011/4/18 Virus 753...@bugs.launchpad.net
It`s working great! Many thanks!
excellent, thanks for the feedback.
I've just committed it upstream (r2972)
the changeset will be available on the NUT Trac mirror (just give it some
minutes to sync):
2011/4/16 Virus 753...@bugs.launchpad.net
$ upsc battery.type
Error: Unknown UPS
$ upsc ups.status
Error: Unknown UPS
damn, I missed a bit (ie the device name):
$ upsc powercom battery.type
Error: Unknown UPS
$ upsc powercom ups.status
Error: Unknown UPS
don't forget to run upsd in debug
2011/4/16 Virus 753...@bugs.launchpad.net
$ upsc battery.type
Error: Unknown UPS
$ upsc ups.status
Error: Unknown UPS
damn, I missed a bit (ie the device name):
$ upsc powercom battery.type
Error: Unknown UPS
$ upsc powercom ups.status
Error: Unknown UPS
don't forget to run upsd in debug
2011/4/7 Virus 753...@bugs.launchpad.net
Public bug reported:
Binary package hint: nut
I have Powercom UPS and trying configure it with NUT.
lsusb:
Bus 006 Device 002: ID 0d9f:0004 Powercom Co., Ltd
ups.conf:
[powercom]
driver = usbhid-ups
port = /dev/usb/hiddev0
2011/4/16 Virus 753...@bugs.launchpad.net
Seems driver respond correctly, but upsd return Broken pipe after:
25.768861 write: [destfd=6] [len=35] [VAR powercom battery.type PbAc
]
Two lines?
yup, but upsd sends everything. and upsc brokes the pipe.
the driver is still there, so the
2011/4/7 Virus 753...@bugs.launchpad.net
Public bug reported:
Binary package hint: nut
I have Powercom UPS and trying configure it with NUT.
lsusb:
Bus 006 Device 002: ID 0d9f:0004 Powercom Co., Ltd
ups.conf:
[powercom]
driver = usbhid-ups
port = /dev/usb/hiddev0
2011/4/16 Virus 753...@bugs.launchpad.net
Seems driver respond correctly, but upsd return Broken pipe after:
25.768861 write: [destfd=6] [len=35] [VAR powercom battery.type PbAc
]
Two lines?
yup, but upsd sends everything. and upsc brokes the pipe.
the driver is still there, so the
Some side notes and comments on this commit...
2011/4/15 Arnaud Quette aque...@alioth.debian.org
Author: aquette
Date: Fri Apr 15 09:15:16 2011
New Revision: 2969
URL: http://trac.networkupstools.org/projects/nut/changeset/2969
Log:
Refreshed graphic illustrations (provided by Eaton
Hi Petr,
2011/4/15 p...@kubanek.net
Hi,
I am not sure if you are the list to hit with this,
right, this (report guidelines) has been a long sitting item on my TODO!
you've been the final trigger and it's now fixed:
http://www.networkupstools.org/stable-hcl.html#footnotes
feedback welcome.
Hi Antoine,
2011/4/7 GATINEAU, ANTOINE (ANTOINE) antoine.gatin...@alcatel-lucent.com
Hello,
I'm trying to integrate upsmon with my alarm management application.
For that I wan't to use NOTIFYCMD from upsmon. I am having troubles making
everything work together.
I'm using nut version 2.4.3
Hi Márk,
2011/4/4 Márk Csaba mar...@gwyll.eu
Hello,
i have a server which supposed to control three Eaton UPS connected by USB
cables. Each UPS is Eaton NV 2000H. (eaton_1, eaton_2, eaton_3)
The connection is fine with each UPS, if it is configured alone.
If i configure two or all three,
Salut Fabrice
2011/3/27 Fabrice Coutadeur coutade...@gmail.com
Public bug reported:
Binary package hint: nut
Hi,
While I was investigating a FTBFS in collectd:
...
configure:22249: checking for upscli_connect in -lupsclient
configure:22274: i686-linux-gnu-gcc -o conftest -Wall -g -O2
Salut Fabrice
2011/3/27 Fabrice Coutadeur coutade...@gmail.com
Public bug reported:
Binary package hint: nut
Hi,
While I was investigating a FTBFS in collectd:
...
configure:22249: checking for upscli_connect in -lupsclient
configure:22274: i686-linux-gnu-gcc -o conftest -Wall -g -O2
(that they don't give out).
I'd be happy to test if somebody can provide me with this liebert-ups
configuration program. (It was a windows, not-java based software as I
remember).
-Spiros Ioannou
On Tue, Mar 1, 2011 at 16:40, Arnaud Quette aquette@gmail.com wrote:
2011/3/1 Farkas Levente
Hi John,
2011/3/16 John Huong jahu...@gmail.com
Hi,
Just started using NUT with a Liebert PSI-XR 3000 with an Intellislot web
card.
It seems I can't get it to run properly.
I am using NUT 2.6.0 built from source on Ubuntu 8.0.4 .
My build parameters are :
./configure --enable-strip
Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
On Mar 23, 2011 5:29 PM, Arnaud Quette aquette@gmail.com wrote:
Hi John,
2011/3/16 John Huong jahu...@gmail.com
Hi,
Just started using NUT
Hi Sergey,
2011/3/21 Sergey Talchuk tals1...@gmail.com
Arjen de Korte nut+users at de-korte.org writes:
Citeren Sergey Talchuk tals1975 at gmail.com:
2. lsusb output
Bus 002 Device 001: ID :
Bus 002 Device 002: ID 0925:1234 Lakeview Research
Your UPS might be
Chetan,
have you been able to look at Arjen's request?
please provide him help to fix HPUX support.
@Arjen: if you want to test some possible fixes, you can commit on the HPUX
branch, so that Chetan can test it without the need for buildbot slaves.
cheers,
Arnaud
2011/3/18 Arjen de Korte
Hi Arjen,
just to revive the static code analysis thread...
It would be nice if you could expose your ideas and the results of your
tests.
Also, apart from Splint, have you tested any other systems?
From what I see, Splint and Frama-C are probably the most interesting.
2010/2/17 Arnaud Quette
2011/3/17 Arjen de Korte nut+us...@de-korte.org
Citeren Charles Lepple clep...@gmail.com:
Arjen: do we actually have any cases of reports larger than 8 bytes?
Yes. At least the MGE Evolution series uses reports that are larger than 8
bytes.
some Eaton and Dell models too
If so,
Hi Niels Kristian,
2011/3/14 Niels Kristian Jensen n...@internetgruppen.dk
We had a power outage and everything went as expected:
The UPS kicked in, it ran for 11 min while charge dropped from 100% to 10%,
then it shut down the host.
When power was restored - 3 hours later - the UPS and
2011/3/11 Charles Lepple clep...@gmail.com
On Mar 10, 2011, at 4:41 PM, Lukas Haase wrote:
However, after upgrading from Debian lenny to Debian squeeze (version
2.4.3-1.1squeeze1) I get the messages in syslog:
ACL in upsd.conf is no longer supported - switch to LISTEN
ACCEPT in upsd.conf
--
Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
2011/2/24 Arnaud Quette aquette@gmail.com
2011/2/22 Roy
Hi Laurent
2011/3/2 Laurent Bigonville bi...@debian.org
Package: nut
Severity: normal
Version: 2.4.3-1
Tags: upstream
Hi,
Lintian is giving us a warning about a powercom.8 man page
nut: manpage-has-errors-from-man usr/share/man/man8/powercom.8.gz 114:
warning [p 2, 2.5i]: can't break
Hi,
2011/2/28 Farkas Levente lfar...@lfarkas.org
Hi,
Thanks for the update, but this patch still not contains the fixes for:
- usb serial cable
- and the shutdown process to properly shutdown the ups.
I merged your patch with our patch (and test it) and attach it to this
mail. IMHO it
2011/3/1 John Bayly freebsd.po...@tipstrade.net
On 25/02/2011 20:35, Arnaud Quette wrote:
Hey Charles,
2011/2/25 Charles Lepple clep...@gmail.com
On Fri, Feb 25, 2011 at 3:21 AM, Arnaud Quette aquette@gmail.com
wrote:
2011/2/25 Charles Lepple clep...@gmail.com
On Thu, Feb
2011/3/1 John Bayly freebsd.po...@tipstrade.net
On 01/03/2011 15:20, Arnaud Quette wrote:
2011/3/1 John Bayly freebsd.po...@tipstrade.net
On 25/02/2011 20:35, Arnaud Quette wrote:
Hey Charles,
2011/2/25 Charles Lepple clep...@gmail.com
On Fri, Feb 25, 2011 at 3:21 AM, Arnaud
2011/2/14 Ernest Sales ersa...@gmail.com
Arjen de Korte nut+us...@de-korte.org va escriure:
This is a known problem in nut-2.4.3 and should be solved in
nut-2.6.0. We have also dropped the megatec and megatec_usb drivers,
so it is probably a good idea to check out the newer release.
If
2011/2/25 Charles Lepple clep...@gmail.com
On Thu, Feb 24, 2011 at 10:36 AM, Arnaud Quette aquette@gmail.com
wrote:
Hi Charles,
2011/2/18 Charles Lepple clep...@gmail.com
On Feb 17, 2011, at 8:41 AM, Arnaud Quette wrote:
Hi John,
2011/1/17 John Bayly
On 14/01/2011 20
Hey Charles,
2011/2/25 Charles Lepple clep...@gmail.com
On Fri, Feb 25, 2011 at 3:21 AM, Arnaud Quette aquette@gmail.com
wrote:
2011/2/25 Charles Lepple clep...@gmail.com
On Thu, Feb 24, 2011 at 10:36 AM, Arnaud Quette aquette@gmail.com
wrote:
Hi Charles,
2011/2/18
2011/2/22 Roy Sigurd Karlsbakk r...@karlsbakk.net
Hi all
Hi Roy
We're considering getting some Powerware 9355-30-M-0 UPSes to replace some
older ones, so I wonder if it would be possible to use NUT for this. It
seems 9315 is supported, but AFAICS that's the top model.
we (Eaton) are
Hi Charles,
2011/2/18 Charles Lepple clep...@gmail.com
On Feb 17, 2011, at 8:41 AM, Arnaud Quette wrote:
Hi John,
2011/1/17 John Bayly
On 14/01/2011 20:40, Arnaud Quette wrote:
Author: aquette
Date: Fri Jan 14 20:40:06 2011
New Revision: 2832
URL: http://trac.networkupstools.org
Hallo Tobias,
2011/2/22 Tobias Frost t...@coldtobi.de
Hallo,
I own a NETUPS 450 (Model on the sticker: PRM 450i; upsstats reports
UPS 450 VA FW -0024) which perfectly works with the upscode2 driver.
Maybe you want to add it to your list, even if the model is 10 years
old.
thanks a lot for
Maintainer: Arnaud Quette aque...@debian.org
Changed-By: Arnaud Quette aque...@debian.org
Description:
libupsclient1 - network UPS tools - client library
libupsclient1-dev - network UPS tools - development files
nut- network UPS tools - core system
nut-cgi- network UPS tools - web
Hi John,
2011/1/17 John Bayly
On 14/01/2011 20:40, Arnaud Quette wrote:
Author: aquette
Date: Fri Jan 14 20:40:06 2011
New Revision: 2832
URL: http://trac.networkupstools.org/projects/nut/changeset/2832
+link:
http://www.networkupstools.org/source/2.6/nut-2.6.0.tar.gz.sig[signature
2011/2/15 Lupe Christoph
On Monday, 2011-02-14 at 21:54:20 -, Arnaud Quette wrote:
I definitely need more info!
please reply to ALL:
- what is the exact model and date of manufacturing?
SmartUPS 300I NET. I have the serial number (GS9809283199) but no date.
it seems
2011/2/15 Lupe Christoph
On Monday, 2011-02-14 at 21:54:20 -, Arnaud Quette wrote:
I definitely need more info!
please reply to ALL:
- what is the exact model and date of manufacturing?
SmartUPS 300I NET. I have the serial number (GS9809283199) but no date.
it seems
2011/2/15 Lupe Christoph
On Monday, 2011-02-14 at 21:54:20 -, Arnaud Quette wrote:
I definitely need more info!
please reply to ALL:
- what is the exact model and date of manufacturing?
SmartUPS 300I NET. I have the serial number (GS9809283199) but no date.
it seems
I definitely need more info!
please reply to ALL:
- what is the exact model and date of manufacturing?
- are you sure this unit is ok?
- have you really checked the cabling or made the whole (cable + UPS) work
somehow (using APC's software or apcupsd)?
- what is the meantime between occurrences
I definitely need more info!
please reply to ALL:
- what is the exact model and date of manufacturing?
- are you sure this unit is ok?
- have you really checked the cabling or made the whole (cable + UPS) work
somehow (using APC's software or apcupsd)?
- what is the meantime between occurrences
2011/2/13 Arjen de Korte nut+de...@de-korte.org
Citeren Richard Gerth r.gerth@gmail.com:
I'd be happy to do testing.
Just let me know when...
In order to get some useful feedback for the -pre versions may I suggest to
subscribe people that are willing to test upcoming releases to
2011/2/11 Arjen de Korte nut+de...@de-korte.org
Citeren Philip Tait phi...@naoj.org:
Would appreciate guidance on getting started generating a MIB-to-NUT
mapping (tools, etc):
OS: CentOS 5.5
NUT version 2.6.0
Assuming that you're able to successfully build NUT from sources, you're
Hi Christoph,
2011/2/10 Lupe Christoph
Since the supposed fix, I have had several ne incidents of this bug.
I'm now running Maverick Meerkat, and the log shows this:
Feb 10 14:10:14 alanya apcsmart[3238]: Communications with UPS lost:
Communications with UPS lost - check cabling
Feb 10
Hi Christoph,
2011/2/10 Lupe Christoph
Since the supposed fix, I have had several ne incidents of this bug.
I'm now running Maverick Meerkat, and the log shows this:
Feb 10 14:10:14 alanya apcsmart[3238]: Communications with UPS lost:
Communications with UPS lost - check cabling
Feb 10
2011/2/7 Kevin bakd...@gmail.com
On 06/02/2011 21:42, Kevin wrote:
on 06/02/2011 21:06 Charles Lepple wrote:
It looks like the only uncommented code which talks to the device is
the last line. (The results from the getval() calls do not seem to be
used.)
APCDelayBeforeReboot maps to
Hi Mike
2011/1/22 Mike. the.li...@mgm51.com
This morning I finished building and configuring nut 2.6.0 on OpenBSD
4.8, and it is running fine.
While I was in the config files, I noticed what looks like it may be a
discrepancy between the config file commetns and the configure script
2011/1/27 Frédéric Bohé fredericb...@eaton.com
On mer., 2011-01-26 at 18:27 +0300, Paul Fertser wrote:
It fixed the issue indeed (though probably seeing Using _existing_ in
the
resulting manpage is a bit confusing).
Indeed but we have not any clean solution for this issue for the moment,
Hi David, Raphael and the Augeas list,
just a small note to mention that NUT - Network UPS Tools lenses are
available, since NUT 2.6.0 release.
These are included in the official release, in the scripts/augeas directory:
http://www.networkupstools.org/download.html
Hi David, Raphael and the Augeas list,
just a small note to mention that NUT - Network UPS Tools lenses are
available, since NUT 2.6.0 release.
These are included in the official release, in the scripts/augeas directory:
http://www.networkupstools.org/download.html
Hi Charles
2011/1/28 Charles Lepple clep...@gmail.com
It looks like there was an issue with the AsciiDoc merge from the trunk:
http://buildbot.networkupstools.org/private/nut/builders/Ubuntu-lucid-x86/builds/119/steps/compile/logs/stdio
mea culpa: Emilien asked me to double check
Hi Stuart,
2011/1/24 Stuart Rackham srack...@gmail.com
On 17/12/10 10:53, Arnaud Quette wrote:
Hi Stuart and the list,
we're still finalizing AsciiDoc integration in NUT:
the dedicated branch has been merged into the trunk (over 1 Mb), few
things
remain and the 2.6.0 release is still
Hi Stuart,
2011/1/24 Stuart Rackham srack...@gmail.com
Hi Arnaud
Congrats on your shiny new documentation!
Nice to see a big project done using AsciiDoc and nice use of JavaScript on
the Compatibility page.
I've added it to the list of 'Documents written using AsciiDoc' on the
AsciiDoc
2011/1/24 Hugh Saunders
Apologies, I had forgotten about /lib/udev/rules.d.
I have removed 52-nut-usbups.rules from /etc/udev/rules.d and it still
works (see log below). There must have been some other configuration problem
initially. I have marked this bug as invalid.
(...)
quite probably
Hi Marek,
2011/1/20 Marek 'marx' Grác
Hi,
Arnaud Quette wrote:
Hi Marek and the list,
First of all, happy new year to you all: health, happiness and ... high
availability ;-)
I've just derived a fence_eaton_snmp script, based on fence_apc_snmp.
You'll find attached the diff against
Hi Fabio,
2011/1/24 Fabio M. Di Nitto fdini...@redhat.com
On 1/24/2011 1:18 PM, Arnaud Quette wrote:
Hi Marek,
2011/1/20 Marek 'marx' Grác
Hi,
Arnaud Quette wrote:
Hi Marek and the list,
First of all, happy new year to you all: health, happiness
2011/1/24 Hugh Saunders
Apologies, I had forgotten about /lib/udev/rules.d.
I have removed 52-nut-usbups.rules from /etc/udev/rules.d and it still
works (see log below). There must have been some other configuration problem
initially. I have marked this bug as invalid.
(...)
quite probably
Emilien and all,
2011/1/21 emilien...@eaton.com
Hi all,
I am pleased to announce that NSS port of NUT is finished.
congrats!
Port is fully functionnal (same functionnalities as openssl, and a
not-activated-by-default client certificate validation function) and
successfully tested by
2011/1/16 Zach La Celle lace...@roboticresearch.com
On 01/11/2011 03:38 AM, Arnaud Quette wrote:
Hi Zach,
2011/1/10 Zach La Celle lace...@roboticresearch.com
On 01/06/2011 08:06 AM, Arnaud Quette wrote:
2011/1/5 Zach La Celle lace...@roboticresearch.com
On 01/04/2011 08:20 AM
Network UPS Tools version 2.6.0 has been released.
http://www.networkupstools.org/
Direct access:
- Download: http://www.networkupstools.org/source/2.6/nut-2.6.0.tar.gz
- News: http://www.networkupstools.org/source/2.6/new-2.6.0.txt
- ChangeLog:
Hi
Note that you need to subscribe to this list, in order to post...
2011/1/14 Jonathan Cunliffe subscript...@gadget.org.uk
Hi,
Has anyone managed to get a Plexus UPS talking to their NAS. I've followed
the excellent instructions here
http://forum.qnap.com/viewtopic.php?f=182t=35970start=0
2011/1/14 Charles Lepple clep...@gmail.com
On Jan 13, 2011, at 3:10 PM, Arnaud Quette wrote:
Author: aquette
Date: Thu Jan 13 20:10:15 2011
New Revision: 2825
URL: http://trac.networkupstools.org/projects/nut/changeset/2825
Log:
Remove AsciiDoc hard-coded verbose flag, which can now
2011/1/10 Laurent Bigonville bi...@bigon.be
I've found the issue.
Actually the nut_check_*.m4 are setting *_LDFLAGS instead of *_LIBS, and
due to a toolchain change this become visible (gcc -o testusb testusb.c
-lusb is working but gcc -o testusb -lusb testusb.c is not working
anymore)
2011/1/10 Laurent Bigonville bi...@bigon.be
I've found the issue.
Actually the nut_check_*.m4 are setting *_LDFLAGS instead of *_LIBS, and
due to a toolchain change this become visible (gcc -o testusb testusb.c
-lusb is working but gcc -o testusb -lusb testusb.c is not working
anymore)
2011/1/10 Laurent Bigonville bi...@bigon.be
I've found the issue.
Actually the nut_check_*.m4 are setting *_LDFLAGS instead of *_LIBS, and
due to a toolchain change this become visible (gcc -o testusb testusb.c
-lusb is working but gcc -o testusb -lusb testusb.c is not working
anymore)
2011/1/13 Arnaud Quette aque...@alioth.debian.org
Author: aquette
Date: Thu Jan 13 12:38:32 2011
New Revision: 2821
URL: http://trac.networkupstools.org/projects/nut/changeset/2821
Log:
Fix the wrong use of *_LDFLAGS instead of *_LIBS, which break compilation
on newer toolchains like
2011/1/13 Charles Lepple clep...@gmail.com
On Jan 13, 2011, at 7:48 AM, Arnaud Quette wrote:
2011/1/13 Arnaud Quette aque...@alioth.debian.org
Author: aquette
Date: Thu Jan 13 12:38:32 2011
New Revision: 2821
URL: http://trac.networkupstools.org/projects/nut/changeset/2821
Log:
Fix
Hi,
2010/12/27 김기세 point...@naver.com
First of all, thanks for your effort to NUT Project,
I'm developing remote monitoring solution for many devices based on linux
server.
In field test, we reached the power shutdown problem which may cause the
crack of linux file system.
I search the
-
De: Arnaud Quette aquette@gmail.com
A: Christoph von Wittich witt...@hentschke-bau.de, goudard sabine
sabine.goud...@st-etienne.archi.fr
Copie à: NUT Users nut-upsuser@lists.alioth.debian.org
Date: Sat, 18 Dec 2010 00:56:09 +0100
Hi Zach,
2011/1/10 Zach La Celle lace...@roboticresearch.com
On 01/06/2011 08:06 AM, Arnaud Quette wrote:
2011/1/5 Zach La Celle lace...@roboticresearch.com
On 01/04/2011 08:20 AM, Arnaud Quette wrote:
2011/1/4 Charles Lepple clep...@gmail.com
On Mon, Jan 3, 2011 at 8:29 AM, Zach
2011/1/11 Arjen de Korte nut+us...@de-korte.org nut%2bus...@de-korte.org
Citeren Mick michaelkintz...@gmail.com:
(...)
PS. What is the meaning of: battery.capacity: 0.03 ?
This is a mapping problem. The UPS is reporting 100% battery capacity is
available and I mistakenly mapped this to
for the fence_eaton_snmp agent is identical to the existing
+fence_apc_snmp agent, upon which it has been derived.
+
+--Arnaud Quette - arnaudque...@eaton.com
diff --git a/fence/agents/eaton_snmp/fence_eaton_snmp.py
b/fence/agents/eaton_snmp/fence_eaton_snmp.py
new file mode 100755
index 000..b02cfd1
2011/1/10 Arjen de Korte nut+de...@de-korte.org nut%2bde...@de-korte.org
Citeren emilien...@eaton.com:
The main reason is to homogenize directive names between apps (mainly
upsmon which uses CERTPATH and upsd which uses CERTNAME) to set the same
property.
Why? The use of CERTFILE
Hi Philip,
2011/1/8 Phillip Susi ps...@cfl.rr.com
The FAQ mentions how to configure nut to pass the power information to HAL
so that gnome-power-manager can display it, but HAL has been depreciated and
removed from Ubuntu since 2007. Has nut been updated to worth with UPower
instead?
no,
Hi Mick
2011/1/9 Mick michaelkintz...@gmail.com
(Apologies for the long message, but there's a lot to report here.)
After a lot of help from Kjell (thank you!) I am now testing the
2.6.0-pre1 version with a usbhid-ups that recognises my UPS:
# /etc/init.d/upsdrv start
* Starting UPS
Hi Michael,
2011/1/7 Michael Hatzakis Jr MD m...@hatzakis.net
Michael
Michael Hatzakis, Jr MD
Physical Medicine and Rehabilitation
you have probably missed a piece of your mail ;-)
cheers,
Arnaud
--
Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com
Network UPS Tools
2011/1/5 Arjen de Korte nut+de...@de-korte.org nut%2bde...@de-korte.org
Citeren Arnaud Quette aquette@gmail.com:
I would be grateful if another developer can pick this up.
I'll check that Arjen.
Never mind, I found the time today to make the necessary changes. I just
committed
2011/1/10 emilien...@eaton.com
Hi Arjen, Hi all,
The main reason is to homogenize directive names between apps (mainly
upsmon which uses CERTPATH and upsd which uses CERTNAME) to set the same
property.
Note that the CERTFILE directive is working but is just flagged as
deprecated.
As ssl
2011/1/5 Zach La Celle lace...@roboticresearch.com
On 01/04/2011 08:20 AM, Arnaud Quette wrote:
2011/1/4 Charles Lepple clep...@gmail.com
On Mon, Jan 3, 2011 at 8:29 AM, Zach La Celle
lace...@roboticresearch.com wrote:
On 12/29/2010 10:00 AM, Zach La Celle wrote:
On 12/29/2010 08:34
Hi Arjen,
best wishes for 2011 to you and your family.
and also to all the list...
2011/1/4 Arjen de Korte nut+de...@de-korte.org nut%2bde...@de-korte.org
I've just committed a rough version of the idowell-hid subdriver to the
trunk. It is already integrated in the usbhid-ups, but I lack the
Hi Michael Hatzakis Jr
2011/1/2 Michael Hatzakis Jr m...@hatzakis.net
Arnaud Quette,
I have read in depth your page regarding APC UPS programming. I hope you
don’t mind taking a moment to assist me. I see that Russel Kroll has long
since retired. I read your APC smart protocol page
2011/1/4 Charles Lepple clep...@gmail.com
On Mon, Jan 3, 2011 at 8:29 AM, Zach La Celle
lace...@roboticresearch.com wrote:
On 12/29/2010 10:00 AM, Zach La Celle wrote:
On 12/29/2010 08:34 AM, Charles Lepple wrote:
On Dec 27, 2010, at 9:36 AM, Zach La Celle wrote:
I ran this in
, test and monitor your devices will greatly improve the
situation.
many pieces of this are already in place. so 2.8.0 should be there quite
quickly.
On Mon, Jan 3, 2011 at 3:43 PM, Arnaud Quette arnaud.que...@free.fr wrote:
Hi James,
2011/1/1 Among The Living stinkysmelly...@gmail.com
Hey
Hi James,
2011/1/1 Among The Living stinkysmelly...@gmail.com
Hey there,
After a few hours with tampering I got my UPS up and running.
It's a RocketFish 1025/1000va (The model varies and is listed as
1000va as well as 1025va).
I got it working with the usbhid-ups driver, which I guess is
Network UPS Tools version 2.6.0-pre1 has been released.
http://www.networkupstools.org/
Direct access:
- Download:
http://www.networkupstools.org/source/2.6/testing/nut-2.6.0-pre1.tar.gz
- News: http://www.networkupstools.org/source/2.6/testing/new-2.6.0-pre1.txt
- ChangeLog:
2010/12/24 Arnaud Quette aquette@gmail.com
2010/12/22 Arjen de Korte adkorte-gu...@alioth.debian.org
Author: adkorte-guest
Date: Wed Dec 22 20:31:42 2010
New Revision: 2777
URL: http://trac.networkupstools.org/projects/nut/changeset/2777
Log:
Don't version generated files
Deleted
2010/12/22 Arjen de Korte adkorte-gu...@alioth.debian.org
Author: adkorte-guest
Date: Wed Dec 22 20:31:42 2010
New Revision: 2777
URL: http://trac.networkupstools.org/projects/nut/changeset/2777
Log:
Don't version generated files
Deleted:
trunk/scripts/hal/ups-nut-device.fdi.in
2010/12/20 Alexander Todorov atodo...@otb.bg
Hello,
there's a recent thread about this or very similar model but without much
info:
http://lists.alioth.debian.org/pipermail/nut-upsdev/2010-October/004968.html
I have this UPS and I'm trying to use it with nut-2.4.3 and megatec_usb
driver:
salut Laurent,
2010/12/21 Laurent Bigonville bi...@debian.org
Le Mon, 20 Dec 2010 21:49:14 +0100,
Arnaud Quette aquette@gmail.com a écrit :
Bonjour Laurent
Salut,
sorry for the time taken to answer, but I'm currently busy preparing
NUT 2.6.0 (for the end of the week).
As debian
Hi Sabine and Christoph,
2010/12/18 Arnaud Quette aquette@gmail.com
Hi Sabine and Christoph,
I've just committed a few changes to mge-utalk (r2749).
can you please try a snapshot and report back the results:
http://new.networkupstools.org/download.html#Snapshots
following Christoph's
901 - 1000 of 2433 matches
Mail list logo
