similar to: NUT 2.6.0-1 for Windows Beta package released

Hi, I have an Eaton 5SC UPS with only 1 USB communication port, but... I need 3 devices to safely switch off in case of power failure, 2 Synology NAS and 1 PC under Windows 7 (soon 10)! So I've decided to connect the UPS to the main NAS (via the USB cable), enabled the "Network UPS server" on the NAS, entered the other NAS and PC IP addresses to let them receive NUT messages in case

[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

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

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 -

Hi Roger, Thanks very much for your answer. I appreciate! > The silence says that there is currently very little interest in NUT on > Windows, and to the best of my knowledge no-one is working on it. I would not argue the fact that there's obviously less interest in NUT on Windows than on Linux. But still, some few comments: 1/ There's maybe LESS interest, but there's some

Hi, Another beginner question. I spend hours trying to find the solution for how to configure winnut properly but I' struggling to make it work. I want my QNAP NAS TS-231 to work as a master and send signal to the PC to shut it down during power outage. I configured QNAP properly (like this: http://geekbeat.tv/qnap-adding-external-devices-qnap), but I don't know what to do next. I work

I changed IP to NAS IP instead of my PC IP and also used NAS login and pass. Didn't work. When I wanted to launch WinNUT with new settings I got: "Fatal error: insufficient power configured!" (same as before) I got this log: Level INFO 10/26/2016 10:46:17 Detected OS as Windows NT Level NOTICE 10/26/2016 10:46:17 Network UPS Tools upsmon 2.0.0.4 Level INFO

[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

Hi, Two weeks and no answer. Any direction how to setup a NUT client on Windows? Any kind of documentation anywhere, even a single page? And if I'm not at the right place, where can I find any help? Any one I should get in touch with? There's at least a developer who did this full port to Window? Thanks for your help! Emmanuel Le mar. 29 oct. 2019 à 00:30, <planet.et at

Hello Folks, I have a couple of questions - one about a basic UPS choice I am to make for a small UK office environment and the second about NUT Windows support. For the UPS, I have 2 or 3 servers, a phone system and a switch i.e. a basic : - Dell R410 1U (2x IEC) - Dell SC1425 1U (1x IEC) - Mitel 3300 CXi phone system (1x IEC) - Netgear GS748T switch (1x IEC) It would be good to also be able

Hello. I've tried to configure Windows (complete port, Beta): Windows MSI installer 2.6.0-1 with my Powerware 5115 connected via USB port but have no luck. Here is my config files: *nut.conf:* MODE = netserver *ups.conf:* [PW5115] driver = bcmxcp_usb port = notUsed desc = "PowerWare 5115" *upsd.conf:* LISTEN 192.168.1.12 3493 *upsd.users:* [monuser]

Hi guys, Thanks very much for your answers! > ...but there's only so much documentation that can cover all the workarounds. > At some point, you need a Windows developer to fix the issues, and to propose > ways to handle things in the source tree that can work for both Windows and > POSIX systems. > > There were some serious problems with the original Windows port branch

Hi, Frederic, big thanks for your work on this, by a coincedence it's exactly what i need at work :) I'm compiling your branch on Debian GNU/Linux with mingw and having some minor troubles worth mentioning and (i hope) fixing. I configure with CC=586-mingw32msvc-gcc ./configure --host=i586-mingw32msvc --prefix=/c/winnut/ Interestingly, there's scripts/Windows/Makefile in the repo

I am aware of 2 windows nut clients both interestingly called winnut. One (winnut 2.0.0b) is a service based client based on a port of the but client code (I think). The other is a GUI client based on (I think again) on knutclient . I have corresponded with both authors about a feature request - to allow the shut-down action to be (optionally) a windows hibernate. This seems a very

Hi All! This time I'm using Nut 2.2.0, Debian etch and kernel v. 2.6.23.9. My hardware config is quite simple. There are 2 PCs connected to my PowerMust 600VA. One is mensioned above the other is a Windows PC using Winnut 2.0.0b. The Linux PC is connected to the UPS via a serial cable and acts as the server. The problem is that both upsmon and winnut disconnect regularly but in random

On Fri, 7 Sep 2018, Ong, Kevin wrote: > Any comments here? I am not a WinNUT user, but in general NUT clients do not produce their own log files. If you want more detail, you have to set the debug options and then look in your system logs. Upsmon.conf MONITOR ups at pfsense 1 <username> <password> slave ... POWERDOWNFLAG /usr/local/ups/etc/killpower My

Hello, I am currently working on the nut scanner. For detecting available upsd on the network, I rely on upscli_connect. The problem with this function is that it calls a blocking "connect" function. So the nut-scanner is blocked while waiting for the TCP timeout when trying to connect to an IP without upsd available . Since this timeout may be rather long (3 minutes on my host), I

Hello, I am currently working on getting rid of libraries dependencies from nut-scanner. Currently nut-scanner depends on several external libs (avahi, snmp, neon, usb). This becomes a nightmare in terms of distribution. So Arnaud asked me to dynamically link those libraries so we come back to a viable package. To do this, I ended up choosing libltdl for a portable implementation but I have

2012/10/12 Emilien Kia <kiae.dev at gmail.com> > Hi guys, > Hi Emilien and the list, This is a pull request to finally merge NSS feature in nut trunk: > https://github.com/clepple/nut/pull/3 > I'd like to take a moment to shed some more light on this important development, which lasted 3 years: - the initial

Thank You very much !!! Now I see how was entered the master password in the file : "-v "concat(' password = ',//system/password)" -n \" I will test the proposed solution. Two questions - Do I need separate users for each WinNUT client or they can use the same user for monitoring&shutdown client machines ? - This is maybe a newbie question,