search for: 90disruptive

...larger experiments but have a computer or VM (with USB/Serial port pass-through) to spare, it may be helpful to build current NUT code base there and test support-ability of the device with it, see: https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests Hope this helps, Jim Klimov On Fri, Apr 19, 2024 at 12:41?PM Stefan Kern via Nut-upsdev < nut-upsdev at alioth-lists.debian.net> wrote: > Heya, > > first time posting to a mailing list so please excuse me if I do something > wrong :) > > I'm new to NUT and try...

...; > On Sat, Sep 16, 2023 at 10:09?AM FatGear via Nut-upsdev < > nut-upsdev at alioth-lists.debian.net> wrote: > >> Hi, >> >> I tried all commands on >> >> https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests >> >> but i don't know what i'm supposed to do next, it seams to download some >> things on my /tmp/nut/ but i don't know what is it. >> >> My kernel is Linux 5.4.0-162-generic x86_64 and i don't have >> huawei-ups2000 driver. >> >&...

...3 at 10:09?AM FatGear via Nut-upsdev >> <nut-upsdev at alioth-lists.debian.net> wrote: >> >> Hi, >> >> I tried all commands on >> https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests >> >> but i don't know what i'm supposed to do next, it seams to >> download some >> things on my /tmp/nut/ but i don't know what is it. >> >> My kernel is Linux 5.4.0-162-generic x86_64 and i don't have >&...

...during the time to make it simple to type, so finally posted a Wiki article that I hope to refer to in such situations from now on. Perhaps it would be useful not only to "newcomers": https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests Jim -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20230119/dad10d62/attachment.htm>

...during the time to make it simple to type, so finally posted a Wiki article that I hope to refer to in such situations from now on. Perhaps it would be useful not only to "newcomers": https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests Jim -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20230119/dad10d62/attachment.htm>

...hat code branch and confirm its log messages behave just as theoretically expected :) An in-place build routine (and references to build prerequisites, if someone here lacks them), can be found at https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests PR source is at https://github.com/jimklimov/nut/tree/issue-1970-throttle - or for code building purposes: :; git clone https://github.com/jimklimov/nut.git -b issue-1970-throttle nut-issue-1970 :; cd nut-issue-1970 # ... follow the Wiki about prerequisites and build procedure -----------...

...iterations on the modified code (especially if the first attempt does not get it right, or if there would be some more work needed beside "knowing" a couple of new IDs) :) The Wiki article https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests details custom builds of NUT for testing from the build workspace (not necessarily installing into the OS) and prerequisites for a number of platforms based on experience with the NUT CI farm summarized at https://networkupstools.org/docs/user-manual.chunked/_build_prerequisites_to_make_nut_f...

...rations on the modified code (especially if the first attempt does not get it right, or if there would be some more work needed beside "knowing" a couple of new IDs) :) The Wiki article https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests details custom builds of NUT for testing from the build workspace (not necessarily installing into the OS) and prerequisites for a number of platforms based on experience with the NUT CI farm summarized at https://networkupstools.org/docs/user-manual.chunked/_build_prerequisites_to_make_nut_f...

Heya, first time posting to a mailing list so please excuse me if I do something wrong :) I'm new to NUT and trying to get things working on my TrueNAS, I have a "Vultech 1500VA" UPS which comes with the software "PowerManager II" and it seems to be using the "richcomm_usb" driver. There are 5 devices in the compatibility list and I tried all of them, sadly to

...at 10:09?AM FatGear via Nut-upsdev < >> nut-upsdev at alioth-lists.debian.net> wrote: >> >>> Hi, >>> >>> I tried all commands on >>> >>> https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests >>> >>> but i don't know what i'm supposed to do next, it seams to download some >>> things on my /tmp/nut/ but i don't know what is it. >>> >>> My kernel is Linux 5.4.0-162-generic x86_64 and i don't have >>> huawei-ups200...

...rly if built in the Debian 11 32-bit environment against libusb-0.1. So to dissect if the issue is between NUT 2.7.4 and 2.8.0 or in the OS environment/dependencies somehow. This can get you started: https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests (take care to `configure --with-usb=libusb-0.1 ...`) - notably, you won't have to *install* this build over what have you in the OS to just test the newly built driver. Jim On Thu, Mar 21, 2024 at 7:18?AM Juan Carlos Fischer < juancarlos.fischer at gmail.com> wrote: > Hello!...

...start, if (packaging) build-time configuration options enable this mode. Given the revised integrations since NUT v2.8.0 release, you might have better luck with current master-branch codebase - see https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests - and by confirming that it works or by uncovering more edge cases that are not well handled, help improve an upcoming NUT v2.8.2 release :) Hope this helps, Jim Klimov On Sat, Jan 20, 2024 at 1:07?PM Stefan Schumacher < > stefanschumacheratwork at gmail.com> wrote: > >>...

...;>> <nut-upsdev at alioth-lists.debian.net> wrote: >>> >>> Hi, >>> >>> I tried all commands on >>> https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests >>> >>> but i don't know what i'm supposed to do next, it seams >>> to download some >>> things on my /tmp/nut/ but i don't know what is it. >>> >>> My kernel is Linux 5.4.0-162-g...

...upsdev < >>> nut-upsdev at alioth-lists.debian.net> wrote: >>> >>>> Hi, >>>> >>>> I tried all commands on >>>> >>>> https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests >>>> >>>> but i don't know what i'm supposed to do next, it seams to download >>>> some >>>> things on my /tmp/nut/ but i don't know what is it. >>>> >>>> My kernel is Linux 5.4.0-162-generic x86_64 and i don&...

...11 32-bit environment against libusb-0.1. >> So to dissect if the issue is between NUT 2.7.4 and 2.8.0 or in the OS >> environment/dependencies somehow. This can get you started: >> https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests >> (take care to `configure --with-usb=libusb-0.1 ...`) - notably, you won't >> have to *install* this build over what have you in the OS to just test the >> newly built driver. >> >> Jim >> >> >> >> On Thu, Mar 21, 2024 at 7:18?AM Jua...

...11 32-bit environment against libusb-0.1. >> So to dissect if the issue is between NUT 2.7.4 and 2.8.0 or in the OS >> environment/dependencies somehow. This can get you started: >> https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests >> (take care to `configure --with-usb=libusb-0.1 ...`) - notably, you won't >> have to *install* this build over what have you in the OS to just test the >> newly built driver. >> >> Jim >> >> >> >> On Thu, Mar 21, 2024 at 7:18?AM Jua...

Hi, this does sound like a useful idea - although for the principle of least surprise and for variation in deployments, I'd rather have it as a (non-default state of a) configuration toggle that can be set via `upsmon.conf`: whether this particular client exits after processing FSD or not. The onus for the rest would be on general systems integration - e.g. ensure that init scripts `K*`ill the