search for: pynut

...etworkupstools/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 when raising without an Exception. (#128) > Date: June 3, 2014 3:34:00 PM EDT > Raising without a valid exception is invalid: > > >>> raise > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > TypeError: excep...

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

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

...mail.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 equivalent) - it will also display GUI notifications. In Debian, it is in the package "nut-monitor". I haven't used this personally, though. Either way, please let us know what we can do to expand the NUT documentation on this topic. -- Charles Lepple clepp...

David, do you have any screenshots of PyNUT that fit this format? Please see Richard's link below. Begin forwarded message: > From: Richard Hughes > Subject: [nut] Please create an AppData file for NUT Monitor (#127) > Date: May 28, 2014 5:37:04 AM EDT > > Please consider writing and installing an AppData file with the...

...ight, that is what upsmon does when the FSD flag is set. > this will cause problem when doing early shutdown at "big-server" > environment (eg: multiple power supply, multiple ups attached to > different host). > > fortunately I found fedora/redhat rpm include the python PyNUT, so I > can write a simple script to set ups FSD without trigger SHUTDOWNCMD. I haven't used PyNUT much, so I am not sure how you would do that. If you want to simulate a power failure on only one UPS, I still recommend using the dummy-ups driver reading from a file. You can then set &quot...

...re how to proceed. To be honest, the install process for the GUI is pretty much "install the distro package", due to the additional dependencies. (I have been trying to install some Python GUI modules from PyPI for another project, and the .deb packages seem way cleaner.) To install the PyNUT module, look for the 'site-packages' directory in the output of this command: python -c 'import sys; print sys.path' Copy PyNUT.py to that directory. (The Debian/Ubuntu/Mint way is to put modules in python-support, then the postinst does some magic to compile the modules into the...

I took v2.8.3-rc in git, bootstrapped autoconf, build, make check, make dist, (on NetBSD 10) and then used that tarball as the source for pkgsrc, built a package, installed it on machine with a Best Fortress (NetBSD 9), rebooted, and both upsc and a program that uses the pyNUT interface code seem fine. So I see no problems. (Of course, I always like there to be a multiday interval from rc to release so I don't mean to hurry you. Just that it looks good to me.)

I took v2.8.3-rc in git, bootstrapped autoconf, build, make check, make dist, (on NetBSD 10) and then used that tarball as the source for pkgsrc, built a package, installed it on machine with a Best Fortress (NetBSD 9), rebooted, and both upsc and a program that uses the pyNUT interface code seem fine. So I see no problems. (Of course, I always like there to be a multiday interval from rc to release so I don't mean to hurry you. Just that it looks good to me.)

Hi David, it seems that your below mail went unmoderated :-/ anyway, any news on the appData side? as usual, I can provide help if needed... have you also been able to take a look at the pyNut3 thread / pull requests? cheers, Arno From: David Goncalves <david at lestat.st> To: Charles Lepple <clepple at gmail.com> Cc: <nut-upsdev at lists.alioth.debian.org> Date: Fri, 30 May 2014 09:34:22 +0200 Subject: Re: Fwd: [nut] Please create an AppData file for NUT Monitor (#12...

...wrote: > I took v2.8.3-rc in git, bootstrapped autoconf, build, make check, make > dist, (on NetBSD 10) and then used that tarball as the source for > pkgsrc, built a package, installed it on machine with a Best Fortress > (NetBSD 9), rebooted, and both upsc and a program that uses the pyNUT > interface code seem fine. > > So I see no problems. (Of course, I always like there to be a multiday > interval from rc to release so I don't mean to hurry you. Just that it > looks good to me.) > > > > > -------------- next part -------------- An HTML attachm...

...wrote: > I took v2.8.3-rc in git, bootstrapped autoconf, build, make check, make > dist, (on NetBSD 10) and then used that tarball as the source for > pkgsrc, built a package, installed it on machine with a Best Fortress > (NetBSD 9), rebooted, and both upsc and a program that uses the pyNUT > interface code seem fine. > > So I see no problems. (Of course, I always like there to be a multiday > interval from rc to release so I don't mean to hurry you. Just that it > looks good to me.) > > > > > -------------- next part -------------- An HTML attachm...

Either I am missing something or I am really STUPID. 1. I have added a user, named nutmon, to the nut group. 2. In upsmon.conf I have set RUN_AS_USER nutmon . 3. I have NOTIFYCMD /etc/nut/notifyme.sh and it is set as 755, so should be executable by everyone. 4. I have the NOTIFYFLAG set as SYSLOG+WALL+EXEC, so the shell should execute. This is the shell script : #!/bin/bash # # NUT NOTIFYCMD

Hello, FYI, I left an ebuild for mgeops in Gentoo Bugzilla under the number 232855.

Maybe it is time to clean up the branches. There are several branches there, that haven't been touched in years. I think we can put several to rest now. Best regards, Arjen -- Please keep list traffic on the list

Fellows, I'm pleased to announce that David Goncalves has now joined the NUT Team. David is working for some time on the NUT Python support, through: - the PyNUT module, which currently provides client access, and which will soon provide some configuration helpers, - the NUT-Monitor client GUI. So, congratulations to David for joining the team! and thanks for his much appreciated contributions in this area... cheers, Arnaud -- Linux / Unix Expert R&D...

On Fri, 16 Sep 2022, Jim Klimov via Nut-upsuser wrote: > Hello all, > ? Here's a PR I want to ask community about: should NUT clients like upsc report (log!) or hide the infamous 'Init SSL without certificate > database' message? How should upsc be used in order to get SSL/TLS protection? There is no configuration file with a CERTFILE declaration. Is there some other way

On Fri, 16 Sep 2022, Jim Klimov via Nut-upsuser wrote: > Hello all, > ? Here's a PR I want to ask community about: should NUT clients like upsc report (log!) or hide the infamous 'Init SSL without certificate > database' message? How should upsc be used in order to get SSL/TLS protection? There is no configuration file with a CERTFILE declaration. Is there some other way

Sorry, that was one mishap layered onto another - the "v2.8.3-rc1" tag was supposed to point to the same commit as what I originally hoped was "v2.8.3"... but did not - instead initially pointed to what would land to `master` among its fixes for a cleaner release. Hopefully tags are correctly refined on GitHub repo now, at least. Jim On Tue, Apr 8, 2025 at 2:58?PM Greg

Sorry, that was one mishap layered onto another - the "v2.8.3-rc1" tag was supposed to point to the same commit as what I originally hoped was "v2.8.3"... but did not - instead initially pointed to what would land to `master` among its fixes for a cleaner release. Hopefully tags are correctly refined on GitHub repo now, at least. Jim On Tue, Apr 8, 2025 at 2:58?PM Greg