similar to: Cleaning up branches

On Sun, Nov 16, 2008 at 11:08 AM, Arnaud Quette <aquette.dev at gmail.com> wrote: > 2008/11/15 Charles Lepple <clepple at gmail.com>: >> On Fri, Nov 14, 2008 at 5:42 PM, Arnaud Quette <aquette.dev at gmail.com> wrote: >>> fellows, >>> >>> You can now commit to the trunk everything that is scheduled for 2.4 >>> >>> For my part,

My UPS Powercom WOW-1000U does greatly work with NUT, but not auto-cofigurable... This UPS is not usb-hid ups, and works well with this settings in NUT: [powercom] desc = "powercom" driver = powercom port = "/dev/serial/by-id/usb-POWERCOM_CO.__LTD._USB_to_Serial-if00-port0" type = IMP lsusb -v fragment attached. Unlike other UPSes, gnome-power-manager does

2007/3/8, Charles Lepple <clepple-guest@alioth.debian.org>: > Author: clepple-guest > Date: Thu Mar 8 04:15:51 2007 > New Revision: 848 > > Modified: > branches/tl_usb_fbsd/drivers/Makefile.am > branches/tl_usb_fbsd/drivers/libhid-uhid.c > Log: > Work-in-progress... maybe I need to look at how the SHUT subdriver works. > ... simply use the same interface

Alexey, I posted this before, but never got a reply. So I'm reposting this again. In the present HID PDC implementation by PowerCOM, expect problems with the non-compliant implementation of the DelayBeforeShutdown and DelayBeforeStartup pages. Third party applications will expect that these follow the HID PDC specifications if you name them like this (and break terribly in the

2006/11/16, Arjen de Korte <adkorte-guest@alioth.debian.org>: > Author: adkorte-guest > Date: Thu Nov 16 21:16:40 2006 > New Revision: 585 > > Modified: > trunk/ChangeLog > trunk/conf/upsd.conf.sample > trunk/server/conf.c > trunk/server/upsd.c > trunk/server/upsd.h > Log: > upsd: add MAXINIT parameter to upsd.conf to make the time upsd

I'm setting up a cluster with multiple ups's using nut 2.2. The ups's are Belkin 1500 (ID 050d:0751) which don't appear to report a serial number. Is there any other way I can setup ups.conf with multiple of these ups over usb on Linux? If I just setup the vendor and product id's, every definition in ups.conf appears to match the first one, and therefore all of them but

fellows, You can now commit to the trunk everything that is scheduled for 2.4 For my part, the november month will be mostly dedicated to the following: - commit the USB "improved maintenance" code. I'm about to finish that one, which allows to extract USB info and generate the various USB related files (hotplug, udev and hal). so the end of that bothering era ^_^ - complete &

On 2/5/2014 8:24 AM, Charles Lepple wrote: > On Feb 4, 2014, at 10:48 PM, Elliot Dierksen wrote: > >> NUT will complain endlessly about communication errors and never establish SNMP communication with my APC UPS > Hmm, at first glance, I read the "complain endlessly" part as a figure of speech, and figured SNMP would get there eventually since it's UDP. But if you have

Hi, Here's the message when I try to stop upsdrv daemon (/etc/init.d/upsdrv stop) * Stopping UPS drivers ... Network UPS Tools - UPS driver controller 2.4.3 Can't open /var/lib/nut/usbhid-ups-auto.pid: No such file or directory Here's the message when I try to start upsdrv daemon (/etc/init.d/upsdrv start) * WARNING: upsdrv has already been started. And finally here's

Hi Charles, Can you give any instructions for installing the NutMonitor. I am looking at the readme in /scripts/python but am unsure how to proceed. I know absolutely nothing about python. Is there no install process for this? On 18/09/17 11:32, Charles Lepple wrote: > On Sep 17, 2017, at 6:33 PM, MTS <mts5204 at bigpond.com> wrote: >> I am using the same configs as I have in

I forgot to cc you guys on the future evolution of the HAL support (it's replacement in fact, called DeviceKit) A mailing list dedicated to DeviceKit is under creation. If some of you are interested in, just answer back. -- Arnaud ---------- Forwarded message ---------- From: Arnaud Quette <aquette.dev at gmail.com> Date: 2008/6/24 Subject: Re: DeviceKit-power patches To: Richard

hi: my testing server has two power supply and attach to two ups. one of the ups is connect to the server with usb. my upsmon.conf like below: # for two ups MONITOR ftups at localhost 1 monmaster nutmaster master MONITOR ftups at 10.1.1.2 1 monslave nutslave slave MINSUPPLIES 1 # for early shutdown NOTIFYFLAG ONBATT EXEC+WALL+SYSLOG NOTIFYFLAG ONLINE EXEC+WALL+SYSLOG NOTIFYCMD

Citeren Arjen de Korte <adkorte-guest op alioth.debian.org>: > Log: > Use the 'nss_compat_ossl' compatibility layer to use the Mozilla NSS > library instead of OpenSSL (we might want to include native support > in the future, but this will at least allow a quick migration for > testing purposes) I don't recall that we ever discussed the possibility of

Hi David, Any thoughts on either this pull request, or #129? https://github.com/networkupstools/nut/pull/128 https://github.com/networkupstools/nut/pull/129 Also note the mention of the new Python module here: https://github.com/george2/python-nut2/tree/development - Charles Begin forwarded message: > From: george2 <notifications at github.com> > Subject: [nut] PyNUT: Fix error

On Sep 22, 2015, at 11:27 AM, Thomas Charron <twaffle at gmail.com> wrote: > > On Tue, Sep 22, 2015 at 9:56 AM, John Hart <jsamcr at gmail.com> wrote: >> notify-send > > notify-send needs a DBUS_SESSION_BUS_ADRESS to work right. Look around for code snippets to get this. Ah, that notify-send. Another option is to launch the PyNUT app in your xsession (or

Citeren Arnaud Quette <aquette op alioth.debian.org>: > Log: > Optionaly enable silent build rules, using AM_SILENT_RULES, only if > it's supported (requires automake 1.11) Why do we need a new branch for this? As far as I can see, only the below lines are really needed > +dnl Currently, we only (force) enable silent rules if available > +dnl Verbose mode can be

hi there, first, kudos to Scott. You guy rock with this revolutionizing (and so logic) idea ;-) next, a personal point of view about the lack of upstream adoption of upstart: I wanted to provide an upstart script for NUT for some time, but never found enough matching example to do so. the embedded scripts only address inittab, and the replacement-initscripts are unreachable (see below) and far

Am 14.10.2016 um 10:19 schrieb Liam O'Toole <liam.p.otoole at gmail.com>: > On 2016-10-13, Valeri Galtsev > <galtsev at kicp.uchicago.edu> wrote: >> >> On Thu, October 13, 2016 11:55 am, Mike - st257 wrote: >>> On Thu, Oct 13, 2016 at 11:33 AM, Valeri Galtsev >>> <galtsev at kicp.uchicago.edu> wrote: >>> >>>

Hi, I'm trying to setup my Mustek 600 with USB (no serial ports on my computer) on Gentoo. The configuration I use is: [Mustek] driver = megatec_usb port = auto desc = "Power Mustek 600 USB" The NUT I use on my x86_64 machine is: sys-power/nut-2.4.3-r2 USE="bash-completion ssl usb xml -cgi -hal -snmp" When I start upsdrv I get: weasel ~ # /etc/init.d/upsdrv start

> Right, I forgot to mention that the explore mode is not meant to send data to upsd - it just generates debug output. And it is written in the man page... that I do had read! > There are a few extra variables that might be read/write, but I don't see the usual ones that translate into commands (such as UPS.BatterySystem.Battery.Test or UPS.PowerSummary.DelayBeforeShutdown). > >