similar to: On retiring some terminology

FYI: PR https://github.com/networkupstools/nut/pull/1328 adds handling of `PRIMARY` alias to `MASTER` on protocol side, hopefully completing the puzzle for issue #840. Reviews and testing would be welcome :) On Sun, Mar 14, 2021, 00:34 Jim Klimov <jimklimov+nut at gmail.com> wrote: > Thanks again for all the suggestions. > > For now I've prepared draft PRs, mostly to map out

FYI: PR https://github.com/networkupstools/nut/pull/1328 adds handling of `PRIMARY` alias to `MASTER` on protocol side, hopefully completing the puzzle for issue #840. Reviews and testing would be welcome :) On Sun, Mar 14, 2021, 00:34 Jim Klimov <jimklimov+nut at gmail.com> wrote: > Thanks again for all the suggestions. > > For now I've prepared draft PRs, mostly to map out

That's odd, seems a spam or phish sneaked through to the list. NOT from me :) Jim On Wed, Mar 23, 2022, 21:38 Jim Klimov via Nut-upsuser via Nut-upsuser < nut-upsuser at alioth-lists.debian.net> wrote: > Hello again, > Please find lower the overall documentation: > > > >

An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20220323/c7ad42ec/attachment.htm>

So, for the past couple of days the SurveyMonkey results are not changing, with 13 replies overall. Should we wait for more or everyone passionate enough has already spoken? In practice I'd likely follow up on a weekend anyway, but... the weekend is coming! :) Currently we have a clear leader pair that collected almost half the votes (6), two votes were to keep old words in place - alas,

So, for the past couple of days the SurveyMonkey results are not changing, with 13 replies overall. Should we wait for more or everyone passionate enough has already spoken? In practice I'd likely follow up on a weekend anyway, but... the weekend is coming! :) Currently we have a clear leader pair that collected almost half the votes (6), two votes were to keep old words in place - alas,

Hello fellow NUTs :) Some time ago an issue https://github.com/networkupstools/nut/issues/840 was raised, and with current work underway to publish a standard on NUT protocol it became more urgent - to retire the master/slave terminology from NUT configuration and documentation. I looked around for suitable synonyms, and for our primary use-case with upsmon roles - where it either manages an

Hello fellow NUTs :) Some time ago an issue https://github.com/networkupstools/nut/issues/840 was raised, and with current work underway to publish a standard on NUT protocol it became more urgent - to retire the master/slave terminology from NUT configuration and documentation. I looked around for suitable synonyms, and for our primary use-case with upsmon roles - where it either manages an

Hello all, As some people watching GitHub closely might have noticed, the majority of proposed changes (for primary/secondary in the end) were merged around weekend. This impacts text documentation and keyword support for upsmon configuration, testing welcome :) Some work remains for image files in documentation, and the protocol/ABI were not touched so far. Following the recent eminent

Hello all, As some people watching GitHub closely might have noticed, the majority of proposed changes (for primary/secondary in the end) were merged around weekend. This impacts text documentation and keyword support for upsmon configuration, testing welcome :) Some work remains for image files in documentation, and the protocol/ABI were not touched so far. Following the recent eminent

Thank you for the suggestions, keep them coming :) To me, I think I considered pub-sub but it did not quite fit - gotta refresh my memory by code re-reading (or expert comments) - I found I'm vague now on who hits the big red button to shout that a particular power source device got critical - the upsmon in "master" role, or "upsd" that talks to all subscribed (indeed!)

Thank you for the suggestions, keep them coming :) To me, I think I considered pub-sub but it did not quite fit - gotta refresh my memory by code re-reading (or expert comments) - I found I'm vague now on who hits the big red button to shout that a particular power source device got critical - the upsmon in "master" role, or "upsd" that talks to all subscribed (indeed!)

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

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

And something else, that previously eluded from my thoughts:my "notifyme" script,i.e the script that is executed at an ups.status="OB" event, is: echo `date` >> /root/upsLog echo " No power, shutting down the system!" >> /root/upsLog sleep 30 control=`/usr/local/ups/bin/upsc Inform@localhost ups.status` if [ $control != OL ] then

Hi I'm having a problem with the bcmxcp_usb driver FSD command: everything seems to work apart from: upsmon -c fsd Environment: Ubuntu 7.04, nut 2.0.5-1, nut-usb 2.0.5-1, Powerware 3105 UPS. upsd appears to send the FSD command to the UPS, upsmon then runs my NOTIFYCMD (which halts my PC) but the UPS just doesn't turn off. Here are the /var/log/daemon.log entries: Jul 24 23:13:16

On Fri, 14 Aug 2020, Todd Benivegna wrote: > https://forum.synology.com/enu/viewtopic.php?f=19&t=73960&hilit=ups+slave  > > I have the latest version of the Windows port of NUT (A UPS management package) installed on my Windows 7 machine. The UPS I am using is a > very old APC BK650M which is controlled and sends its status via a special serial cable to the Windows

Hello, I am a new user of NUT and trying to wrap my ahead around a couple of things. I installed NUT 2.7.4-13 from package on RasPi 4, running Raspbian Linux 11 (bullseye). I have Cyberpower SL700U connected to it. For testing I set battery.charge.low to 90, so I wouldn't have to wait a long time. See all relevant config below. First of all, what seems to happen is that UPS gets to the low

Hi Billy, switching back this thread to -upsdev 2012/2/27 William R. Elliot <bill at wreassoc.com>: > I have been able to set the 'FSD' from the driver and it is picked up by > upsmon.? That gives me the functionality that I was asked to put in the > driver.? If that is against the rules then I'll make an adjustment when the > allowed method is defined.? :-) yup,

Greetings! I have successfully installed and configured nut package. All i want now is to power off ups. If i run upsmon -c fsd as root - everything goes fine, system and ups gracefully shutting down. If i unplug power cable from an ups, then system is down, but ups still on load. Any help would be appreciated. Debian Lenny x86 ups.conf [ippon] driver = megatec port = /dev/ttyS0