similar to: NUT on Windows revival

Back from vacations, and before I dive into real-life work, I went over some ideas and notes from the NUT for Windows effort. Now they should be tracked at https://github.com/orgs/networkupstools/projects/2/views/1 and community help is welcome :) I probably forgot or missed some caveats - so feel free to post issues for this project if you think of some more... Jim On Thu, Jun 23, 2022, 23:52

Back from vacations, and before I dive into real-life work, I went over some ideas and notes from the NUT for Windows effort. Now they should be tracked at https://github.com/orgs/networkupstools/projects/2/views/1 and community help is welcome :) I probably forgot or missed some caveats - so feel free to post issues for this project if you think of some more... Jim On Thu, Jun 23, 2022, 23:52

"Good news, everyone!" With CI builds of the branch now regularly passing on both the multiplatform FOSS NUT CI farm (including linux+mingw cross-builds), and CircleCI with MacOS, and newly on AppVeyor with Windows+MSYS2 (including integration tests with live upsd and some dummy-ups instances), after ironing a few wrinkles I intend to PR and merge it into the main NUT codebase soon,

"Good news, everyone!" With CI builds of the branch now regularly passing on both the multiplatform FOSS NUT CI farm (including linux+mingw cross-builds), and CircleCI with MacOS, and newly on AppVeyor with Windows+MSYS2 (including integration tests with live upsd and some dummy-ups instances), after ironing a few wrinkles I intend to PR and merge it into the main NUT codebase soon,

Windoze in da NUT house! Codebase of the NUT for Windows branch was merged to main codebase, not in the least to avoid bit-rot and need for resynchronisation with merge conflicts that regularly arose as the two branches "just co-existed". More community work is needed to complete some drivers' functionality and MSI package delivery, but for many use-cases it may already "just

Windoze in da NUT house! Codebase of the NUT for Windows branch was merged to main codebase, not in the least to avoid bit-rot and need for resynchronisation with merge conflicts that regularly arose as the two branches "just co-existed". More community work is needed to complete some drivers' functionality and MSI package delivery, but for many use-cases it may already "just

--- Sigmund Augdal <sigmunau@stud.ntnu.no> wrote: > On Sun, Mar 09, 2003 at 03:58:22PM +0100, Sander Roobol wrote: > > Hello Dan Johnson, hello list, > > > > It's really weird that there's no working command line player for > FLAC > > files. Dan Johnson created flac123 (licensed under the GPL) to fill > that > > gap, and started the flac-tools

On Jun 16, 2017, at 6:12 AM, Manuel Wolfshant <wolfy at nobugconsulting.ro> wrote: > > running autogen.sh was triggered automatically. but even if I do it explicitly, I still get: > + autoreconf -i > configure.ac:887: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body

Running NUT version 2.8.2 on Fedora 40. NUT installed from the Fedora package. CyberPower CP1000AVRLCD connected by USB. I updated the system yesterday with all the latest Fedora packages. Now NUT will not run. Chasing the issue through the layers, I come to this: ===================== [root at mythtv rules.d]# upsc cyberpower Error: Driver not connected [root at mythtv rules.d]#

Hello Dan Johnson, hello list, It's really weird that there's no working command line player for FLAC files. Dan Johnson created flac123 (licensed under the GPL) to fill that gap, and started the flac-tools project. Unfortunately, flac123 doesn't work anymore with the latest FLAC, and the flac-tools project has been idle for more than a year. I created a patch that makes flac123

> Previously, the manufacturer tested this UPS on version 2.6.5-6 NUT for Windows. Thanks for this important detail. For immediate re-testing, I would recommend to use either NUT v2.8.0 already packaged by some distributions in their testing/bleeding-edge repositories (unfortunately, during the almost year since release many distros - especially for LTS versions - did not change recipes to

Did the upgrade by chance install/alter any udev rules causing the UPS devices to now have incorrect permissions? And what user is nut running as? On November 9, 2024 9:58:57 AM EST, Bill Gee <bgee at campercaver.net> wrote: >Running NUT version 2.8.2 on Fedora 40. NUT installed from the Fedora package. CyberPower CP1000AVRLCD connected by USB. > >I updated the system yesterday

Nut should be running as user nut. As far as I can tell, the udev rules have not changed. And the system IS seeing the UPS at a low level. I looked through /dev/ but did not see a device that jumps out as the UPS. ===================== [root at mythtv rules.d]# dmesg | grep -i 0764 [ 2.021485] usb 1-1.8: New USB device found, idVendor=0764, idProduct=0501, bcdDevice= 0.01 [ 2.049515]

Cheers, One PR waiting to get into 2.8.1 release timeframe is https://github.com/networkupstools/nut/pull/1652 stemming from issue https://github.com/networkupstools/nut/issues/1279 The gist of it is that "battery.voltage" and "battery.charge" were not always reported correctly with nutdrv-qx driver (might be handled better by blazer drivers though), and the overrides

Check /dev/hidraw6, as noted in your dmesg output (and any other *hid* devices under /dev). User nut has almost zero privs to devices unless a udev rule changes the perms on the dev for nut . . . On November 9, 2024 1:25:29 PM EST, Bill Gee <bgee at campercaver.net> wrote: >Nut should be running as user nut. As far as I can tell, the udev rules have not changed. And the system IS

On 06/18/2017 05:42 PM, Charles Lepple wrote: > On Jun 16, 2017, at 6:12 AM, Manuel Wolfshant > <wolfy at nobugconsulting.ro <mailto:wolfy at nobugconsulting.ro>> wrote: >> >> running autogen.sh was triggered automatically. but even if I do it >> explicitly, I still get: >> + autoreconf -i >> configure.ac:887: warning: AC_LANG_CONFTEST: no

On up-to-date f36, with latest kernel 6.1.7-100.fc36.x86_64. After receiving a few of these messages Broadcast message from nut at e7.eyal.emu.id.au (somewhere) UPS ups at ups is unavailable I noticed and ran sudo systemctl restart nut-driver at ups.service which triggered Broadcast message from nut at e7.eyal.emu.id.au (somewhere) Communications with UPS ups at ups established I now added

On 12/03/2016 08:03 AM, Charles Lepple wrote: > On Dec 2, 2016, at 10:23 PM, Jack McGee <jack at greendesk.net> wrote: >> This is new install on Ubuntu 16.04, using packages from Synaptic, >> Network UPS Tools upsd 2.7.2 >> >> I am getting these messages in the terminal: >> Broadcast message from nut at amethi (somewhere) (Fri Dec 2 12:33:03 2016): >>

I upgraded an operating system to openSUSE 42.2, kernel 4.4 and recompiled nut 2.7.4. ./configure, make clean and make went well, but make install failed. Make reports Making install in clients make[1]: Entering directory '/mnt/home/rprice/nut/nut-2.7.4.dev/clients' make[2]: Entering directory '/mnt/home/rprice/nut/nut-2.7.4.dev/clients' /usr/bin/mkdir -p '/usr/lib64'

Hi Jim Thanks for the info. Nut runs on bare metal, there is no virtualization layer. I will have a look at the github post after writing this post. I have compiled and installed nut 2.8.2 as suggested. But now I am confused: Where is the usb-hid driver, which I used in Nut 2.8.0? Does one need to pass a special flag to configure to build it? Yours Stefan Am Fr., 5. Juli 2024 um 18:52 Uhr