similar to: newhidups and threads (was: suse linux and nut)

2006/10/2, Peter Selinger <selinger@mathstat.dal.ca>: > Arnaud Quette wrote: > > > > 2006/9/29, Peter Selinger <selinger@mathstat.dal.ca>: > > > > > I don't really understand the purpose of the "Testing" branch. It has > > > not been touched since July, as far as I can see. I also don't > > > understand NUT's release

2005/9/25, Peter Selinger <selinger@mathstat.dal.ca>: > > Arnaud Quette wrote: > > > > Some more points while you're at it: > > - newhidups will have to be renamed. My aimed was to let the name until > we > > can superceed hidups. Then remove hidups, and rename newhidups to > usbhid-ups > > (name proposition welcomed, but should match the fact

Hi Shane, please try the instructions at http://www.mathstat.dal.ca/~selinger/ups/backups.html (with appropriate modifications for FreeBSD). If you can't get it to work, please get help from the nut-upsuser mailing list (cc'd above), as I am no longer actively involved in NUT development. Good luck, -- Peter Shane Roberts wrote: > > Hi Peter, > > I am running the NUT

Philipp Leusmann wrote: > > Ok, I tried this and my results seem to bet he same as reported. Then I > think I=B4ll have to stick with the windows-driver at least on my main > machine.=20 > Or is there anything I can help to fix this driver? I don't know why we can't read anything from this device. There are many ways in which one could make a buggy device that works with

Hello everyone! If this message was posted twice, my apologies. I'm having issues with my webmail today... I am using the testing version of NUT from SVN at changeset 582. I have successfully created a stub for newhidups driver for my Dynex DX-800U UPS, but I am completely lost on the customization of it. I've followed the hid-subdrivers.txt instructions and I understand I need to

Fellows, back for 4 days, the baby and the mother are now at home, and the father is... hem, well not so fresh ;-) For those interested in some pictures: http://benjamin.quette.free.fr/ 2006/11/16, Peter Selinger <selinger@mathstat.dal.ca>: > ... > Arnaud: could you please amend the instructions on the NUT download > website http://www.networkupstools.org/source.html (Development

ok, I'll try to sum up the thread and answers to the various point: 2005/10/24, Peter Selinger <selinger@mathstat.dal.ca>: > > Arnaud Quette wrote: > ... > > Any perl (or other well supported scripting) monger out there to take > over > > that one? > > Great idea. How about bash/sh? Still the most universally available > scripting language. I am

Hi Kiko, 2006/2/25, Kiko Piris <menorqui@pirispons.net>: > Package: nut-usb > Version: 2.0.3-1 > Severity: important > > > When newhidups loses comunication with ups (G), it dies when trying to > reconnect with the error: > > *** glibc detected *** double free or corruption (fasttop): 0x08068268 *** > > Following is a copy&paste of the last lines of

Hi Patrick, I didn't get further bug reports from you, so I have now listed your device as "supported" by newhidups. Last I saw as of your below message, the driver was working as expected. If there are any future problems, let me know! -- Peter Patrick Nolan wrote: > > Remember me? Back in May we exchanged some messages about my Tripp-Lite > UPS. My boss has gone on

I have checked in a cleaned-up version of patch #302111 (Belkin support) into CVS. See cvs diff -uN -r before_PSE_2 -r after_PSE_2 to check the difference. Here is the CHANGES entry: Tue Sep 13 20:50:14 UTC 2005 / Peter Selinger <selinger@users.sourceforge.net> - newhidups: added Belkin support. Also added some new variables and instant commands (some of these were already used by

Hi James, thanks for the feedback. The output you get seems generally fine, except for battery.voltage: 0.0 and output.voltage: 164.0; these values are consistent with what Phil DeBoest reported. Upsmon normally executes the shutdown command when you reach the "low battery" threshold, as decided by the UPS and/or driver. It does so by looking at ups.status, not battery.charge. --

Hi Patrick, Patrick Nolan wrote: > > Remember me? Back in May we exchanged some messages about my Tripp-Lite > UPS. My boss has gone on vacation, so I finally got a chance to take a > look at this. > > Peter Selinger wrote: > ... > > In case you feel like experimenting with this, I am attaching a patch > > that *might* enable this device to be supported by the

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

Oh oops, I see you already did. -- Peter selinger wrote: > > You could send it without "submitting" it. That's the advantage of > patches - they can be discussed. There are lots of eyeballs here that > might see what's wrong. Thanks, -- Peter > > Eric S. Raymond wrote: > > > > Peter Selinger <selinger at mathstat.dal.ca>: > > > I

On 1/13/07, Peter Selinger <selinger@mathstat.dal.ca> wrote: > > The question is when exactly this should be converted to a number. > > Should this be done in upscli_splitname() or in upscli_connect()? The > > latter would require a change in the prototypes of upscli_splitname() > > and upscli_connect(), and an attendant change in all the existing > > clients.

Have recently purchased a MGE Nova 1100 UPS and am trying to get running on netBSD. Configuration netBSD 3.0 amd64 libusb 0.1.10a nut 2.0.3 Built & installed libusb Built kernel with ugen device and uhid removed Build & install nut-2.0.3 with usb Chmod /dev/ugen1 etc to allow access by nut user. Ups.conf [MGENova] driver = newhidups port = auto

On 10/15/06, Peter Selinger <selinger@mathstat.dal.ca> wrote: > I have converted NUT's build system to Automake/Libtool. Right now, > the new build system is contained in the "automake" branch, at: Wow... this is really nice. Thanks for taking the time to do the conversion. > drivers/Doxyfile - this seems to belong to Charles. Perhaps >

I tested your fix (newhidups -DDD /dev/null) using both and APC Back-UPS 350 an APC Smart-UPS RT 2000 XL. No more segmentation fault due to the fixed-size array. ~Jacob -----Original Message----- From: nut-upsdev-bounces@lists.alioth.debian.org [mailto:nut-upsdev-bounces@lists.alioth.debian.org] On Behalf Of Peter Selinger Sent: Monday, October 16, 2006 12:12 PM To: Schmier, Jacob Cc: NUT

On 2/10/06, Charles Lepple <clepple@gmail.com> wrote: > On 2/10/06, Peter Selinger <selinger@mathstat.dal.ca> wrote: > > Charles Lepple wrote: > > > > > > > [...] The only thing I had to correct manually is > > > > that a few of my binary files were inaccurately classified as text > > > > files (and thus subject to the \r\n

I'm happy to have had a quick look at this thread... 2007/5/17, Peter Selinger <selinger at mathstat.dal.ca>: > ... > as you know, I haven't had much time to work on NUT. Now my wife is > expecting our first baby in 1 week, so I don't think I will get back > to it in the foreseeable future. I didn't knew before! what a good news: all my congratulations to you