similar to: Windows version development status

Hello dear all, I try to use NUT for windows (not WinNUT), and stuck with launching NOTIFYCMD. On any event marked as SYSLOG+WALL+EXEC syslog entry appears, popup window appears, but NOTIFYCMD script doesn't run. If I run upsmon.exe in cmd (i. e. not as a service) everything works fine. Here is my upsmon.conf: MONITOR central at 10.35.0.180 1 user password slave MINSUPPLIES 1 SHUTDOWNCMD

Greetings, The way that bcmxcp_usb reacts to and recovers from a USB cable unplug-plug appears to have changed significantly between 2.4.1 and 2.6.0. While I can see some improvements, bcmxcp_usb 2.6.0 does not appear to handle a USB cable unplug-plug correctly. Does anyone know if this has been fixed in subsequent releases? Here are the details. When the USB cable between my server and my

Dear Fusion Inventory fellows, I've been thinking about working on adding power devices knowledge to inventory systems for years. Following the last Ubuntu Developer Summit, I know have an "excuse" to do so: https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-cloud-power-management My below proposition is related to the above blueprint. So please keep in mind that the

Hello all, There is a new Windows package of NUT. It now contains nut-scanner binary. Note that there is a known issue with libupsclient.dll with nut-scanner. The scan of NUT servers using nut-scanner will not work for now. You can find it at : http://www.networkupstools.org/source/2.6/NUT-Installer-2.6.3-1.msi Please send feedback to the list. Regards, Fred -- Team Open Source Eaton -

[attachments trimmed] Begin forwarded message: > From: eric kreuwels > Subject: UPSC based Windows Client > Date: October 13, 2013 4:43:31 PM EDT > To: nut-upsdev at lists.alioth.debian.org > > > Dear developers > > Last month I wrote WinUPSC, a Windows task tray UPS monitor. WinUPSC re-uses the UPSC logic to poll the UPS. > This initial version was tested

Hello all, Thanks to early feedbacks from Dmitry Ogorodnikov, we have made a new Windows package of NUT with previously missing DLLs allowing to run netxml-ups and snmp-ups drivers as well as nut-scanner tool. You can find it at : http://www.networkupstools.org/source/2.6/NUT-Installer-2.6.3-3.msi Please send feedback to the list. Regards, Fred -- Eaton Opensource Team -

[Please remember to copy the list.] On Oct 15, 2013, at 8:45 AM, eric kreuwels wrote: > Hi Charles > > Thanks for your answer. Good questions/suggestions. I copied both the WinUPSC and the installer project on my GDRIVE and shared it with you: > https://docs.google.com/file/d/0B0mSjYYj84-6ZGM4MWZfMnFxbUU/edit?usp=sharing > > Archiving WinUPSC in the NUT GitHub would be my

[As posted as Ubuntu Question #184284 on Launchpad] Hi, I try to set up nut (2.4.3) on my Lucid (10.04.3 LTS) to make use of my old but very trusty UPS (Best Power Fortress 660 LI). Yes, this UPS is old (about 16 years), but with its third battery pack last week it is as good as new. It runs perfectly well with Windows XP, Vista and even Windows 7. But not so with Ubuntu and nut. After

Emilien, just saw your commit in Buildbot for testing some Windows changes. That's great that someone is working on this again! We have had a few users ask for updates to the 2.6.5+ version of NUT for Windows. The problem is that we do not have a good branch in Git to work from. The windows_port branch got rebased, but since it has merge commits, it is a bit of a mess. I apologize for

2011/6/27 Frederic BOHE <fbohe-guest at alioth.debian.org> > Author: fbohe-guest > Date: Mon Jun 27 13:56:51 2011 > New Revision: 3060 > URL: http://trac.networkupstools.org/projects/nut/changeset/3060 > > Log: > Add NUT server scan. > > (...) > device_t * scan_snmp(char * start_ip, char * stop_ip,long usec_timeout, > snmp_security_t * sec); > >

2014/1/15 Charles Lepple <clepple at gmail.com>: > Emilien, > > just saw your commit in Buildbot for testing some Windows changes. That's great that someone is working on this again! > We have had a few users ask for updates to the 2.6.5+ version of NUT for Windows. I am just fixing some bugs and implementing some minor windows-specific features. > The problem is that

On Wed, 2013-07-17 at 23:33 -0400, Charles Lepple wrote: > On Jul 17, 2013, at 11:27 AM, Matt Ivie wrote: > > > I'm really just looking for a UPS that might run a couple of small > > servers and other small devices(routers or switches). > > Good call on including the network gear in the power budget. NUT isn't much use to the slave systems if the network

I and several other users have encountered problems using PowerCOM UPS of the BNT 1500A model. Looking over other responses and dealing with my own issues, I submit the following attached patch. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20110428/00d7d2f9/attachment.htm> -------------- next

c'est quoi cette chelouzerie ? je parle de l'ajout du sizeof(DWORD)... et ce que ce serait pas un str*n*cpy ou s*n*printf la vraie solution ? Arno 2012/5/3 Frederic BOHE <fbohe-guest at alioth.debian.org>: > Author: fbohe-guest > Date: Thu May ?3 08:31:38 2012 > New Revision: 3554 > URL: http://trac.networkupstools.org/projects/nut/changeset/3554 > > Log: >

On Tue, 2013-07-16 at 23:09 -0400, Charles Lepple wrote: > On Jul 16, 2013, at 11:30 AM, Matt Ivie wrote: > > > I'm sure this has been asked before and I did search the list archives > > but anything I did find looked to be older. > > > > I'm looking at buying some UPS and I'm not sure how to tell which > > currently sold models are supported by

On Jul 17, 2013, at 11:27 AM, Matt Ivie wrote: > I'm really just looking for a UPS that might run a couple of small > servers and other small devices(routers or switches). Good call on including the network gear in the power budget. NUT isn't much use to the slave systems if the network connection between master and slave goes down. > If I could get > 15-30 minutes of

Device Manufacturer: Eaton Device Name: 5S1500LCD ---------------------------------------------------------- upsc output: battery.charge: 100 battery.charge.low: 20 battery.runtime: 3515 battery.type: PbAc device.mfr: EATON device.model: Ellipse PRO 1500 device.serial: 0000000000 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2

Device Manufacturer: Eaton Device Name: 5S1500LCD ---------------------------------------------------------- upsc output: battery.charge: 100 battery.charge.low: 20 battery.runtime: 3515 battery.type: PbAc device.mfr: EATON device.model: Ellipse PRO 1500 device.serial: 0000000000 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2

Hello, I have trouble connecting to an Eaton 5PX UPS via the usbhid-ups driver. It is supposed to be fully working according to the compatibility list (support level 5). OS: A fresh Debian stable install. Then changed the apt source to unstable and did "aptitute update" and "aptitude install nut". Nothing else. I did that, because the "unstable" package is a more

Hello, As you may have noticed, a first running version of nut for Windows has been released some time ago. In order to validate the possibility to merge the windows_port branch to the trunk, I have produced a patch file using the "svn diff" command. This patch couldn't be applied directly and the use of a merging tool is still needed. It is only intended to be reviewed so that we