similar to: binary files in CVS [was: Character-encoding in code and docs]

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

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

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

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.

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 >

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

[moving to upsdev as it's now off topic for upsusers] 2006/8/30, Peter Selinger <selinger@mathstat.dal.ca>: [snip] > > the threaded method would allow, with some sub-drv config, to launch > > the polling thread and/or the interrupt thread. Either feeding the > > core is not important since the core wouldn't care about that. > > I think is may make sense to

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

I think someone tried this recently, although I cannot find the post any more. It may be helpful, but it is not guaranteed that we will find anything. Could you please keep the discussion on the mailing list? Thanks, -- Peter Philipp Leusmann wrote: > > Wouldn't it help to sniff usb-communication with the windows driver? > > Philipp > > > -----Urspr=FCngliche

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

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

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

was: Re: [Nut-upsdev] usbhid-ups.h: hid_info_t structure On 8/2/07, Peter Selinger <selinger at mathstat.dal.ca> wrote: > All this needs to be replaced by a re-designed, cleaned-up data > structure. It's on my to-do list, but nothing on that list will get > done by me anytime soon. As nothing is technically broken, and the > changes are prone to introducing subtle bugs, this

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

Marc Collin wrote: > > Le mercredi 27 d=E9cembre 2006 00:29, vous avez =E9crit=A0: > > Hi Marc, > > > > the answer to your question is contained in the file INSTALL, > > distributed with NUT, section 6 "Set ownership data and permissions on > > your serial or USB ports that go to your UPS hardware." > > > > Quote: > > > >

Charles Lepple wrote: > > On 11/9/06, Peter Selinger <selinger-guest@alioth.debian.org> wrote: > > Author: selinger-guest > > Date: Fri Nov 10 05:57:37 2006 > > New Revision: 578 > > @@ -566,72 +567,72 @@ > > > > AC_MSG_CHECKING(driver path) > > AC_ARG_WITH(drvpath, > > -AC_HELP_STRING([--with-drvpath=PATH], [where to install ups

Hi I'm sending this to you as it appears that you are the person who looks after and/or supervises the code for NUT's Belkin drivers. I'm using the address you use for the Nut-upsdev mailing list ( selinger at mathstat.dal.ca ). Anyway... I have a Belkin Universal UPS and, having just upgraded my Fedora Core system from 4 to 5 and had to go back through the system RC files

Hi, I am running samba and lprng for 4 hp laserjets. Sometimes a samba print job goes to the wrong printer. Normally everything works just fine. Shown below is the lprng acct log file enries for the concerned print job. Please notice that the print job was supposed to go to hp4050-mail, but ended up in hp8100. Any suggestions are much appreciated. Thanks Balagopal jobstart

Thank you for your response. The point is that I have configured my system to shut down at the event "upsc Inform@localhost ups.status"!="OL", not at "LB". So there will be no /etc/killpower file created. At an ups.status != "OL" event, the following script named "notifyme" is run: echo `date` >> /root/upsLog echo " No power, shutting