search for: klimovs

Displaying 20 results from an estimated 532 matches for "klimovs".

Did you mean: klimov
2025 Jan 12
1
FOSDEM 2025
Hello all, Is anyone planning to be at FOSDEM this year? I'll be in Brussels from Thursday evening to Sunday evening. My Friday is pretty tightly scheduled, but I would love to meet any of you in person during the weekend (or on a Thursday supper) :) Jim Klimov -------------- next part -------------- An HTML attachment was scrubbed... URL:
2025 Jan 12
1
FOSDEM 2025
Hello all, Is anyone planning to be at FOSDEM this year? I'll be in Brussels from Thursday evening to Sunday evening. My Friday is pretty tightly scheduled, but I would love to meet any of you in person during the weekend (or on a Thursday supper) :) Jim Klimov -------------- next part -------------- An HTML attachment was scrubbed... URL:
2024 Apr 01
2
NUT v2.8.2, the Easter Egg Edition
Hello all, After a prolonged labour with a few re-issues of the tag and many pushes during the day, NUT v2.8.2 was found in a strange egg by a bunny hopping away from the April fools. All that - blessed under the shine of Polar lights in the middle of the icy North Ocean. A python module was released but slipped away with an earlier commit. Other artifacts should follow shortly. Jim Klimov
2024 Apr 01
2
NUT v2.8.2, the Easter Egg Edition
Hello all, After a prolonged labour with a few re-issues of the tag and many pushes during the day, NUT v2.8.2 was found in a strange egg by a bunny hopping away from the April fools. All that - blessed under the shine of Polar lights in the middle of the icy North Ocean. A python module was released but slipped away with an earlier commit. Other artifacts should follow shortly. Jim Klimov
2024 Apr 19
1
NUT v2.8.2, the Easter Egg Edition
Errata coming up for NUT v2.8.2: * it was discovered that the nut-driver-enumerator (NDE) script had a regression which caused it to not reload nut-driver instances (systemd, SMF) when `ups.conf` edits happened. * on a related note, it may be possible that "live" driver reloading (at least on master branch) does not reduce debug verbosity to zero when `debug_min 0` is active in its
2024 Apr 19
1
NUT v2.8.2, the Easter Egg Edition
Errata coming up for NUT v2.8.2: * it was discovered that the nut-driver-enumerator (NDE) script had a regression which caused it to not reload nut-driver instances (systemd, SMF) when `ups.conf` edits happened. * on a related note, it may be possible that "live" driver reloading (at least on master branch) does not reduce debug verbosity to zero when `debug_min 0` is active in its
2025 Feb 04
1
FOSDEM 2025
The trip to FOSDEM 2025 was great fun, with many interactions, useful lectures and fruitful conversations. It was insightful to randomly meet at least one person using the project, a few eager to use and asking question, and sadly quite a few who did not recognize not only "NUT" but also "UPS" key words. Face-to-face talks to maintainers of Debian, OpenIndiana, Tribblix and
2025 Feb 04
1
FOSDEM 2025
The trip to FOSDEM 2025 was great fun, with many interactions, useful lectures and fruitful conversations. It was insightful to randomly meet at least one person using the project, a few eager to use and asking question, and sadly quite a few who did not recognize not only "NUT" but also "UPS" key words. Face-to-face talks to maintainers of Debian, OpenIndiana, Tribblix and
2025 Mar 28
5
NUT testing for v2.8.3 (hopefully imminent)
Hello all, It has been too long that I was feeling a release is just around the corner, just gotta tie up a few loose ends. The significant ones we had are finally tied, some others delayed to v2.8.4 trail, and a documentation refresh remains. Thanks to some package maintainers taking a look at the master branch, some issues with "dist" archive creation and parallel builds were also
2025 Mar 28
5
NUT testing for v2.8.3 (hopefully imminent)
Hello all, It has been too long that I was feeling a release is just around the corner, just gotta tie up a few loose ends. The significant ones we had are finally tied, some others delayed to v2.8.4 trail, and a documentation refresh remains. Thanks to some package maintainers taking a look at the master branch, some issues with "dist" archive creation and parallel builds were also
2022 Mar 23
3
On retiring some terminology
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: > > > >
2025 Apr 02
1
NUT testing for v2.8.3 (hopefully imminent)
So... April 1st came and went, busy with last-minute warnings from a newly set-up NetBSD build agent for the NUT CI farm, as Greg-inspired warnings exposed by the stricter platform kept popping up and biting. Led to some discoveries in toolkits and standards I thought I knew for decades, too. So it was a tad bit annoying, but good overall :) But now we are a day over the hopeful "not more
2025 Apr 02
1
NUT testing for v2.8.3 (hopefully imminent)
So... April 1st came and went, busy with last-minute warnings from a newly set-up NetBSD build agent for the NUT CI farm, as Greg-inspired warnings exposed by the stricter platform kept popping up and biting. Led to some discoveries in toolkits and standards I thought I knew for decades, too. So it was a tad bit annoying, but good overall :) But now we are a day over the hopeful "not more
2024 Sep 25
1
SKE UPS 1500VA/900W
I believe the integration is presented as a container on the HA server, so there should be a way to log into it and edit `/etc/nut/ups.conf` or similar during the experiments (generated from YAML settings made in HA GUI somewhere). I have not used it directly, so I can't really help more here. Jim On Wed, Sep 25, 2024 at 5:47?PM Daniele Lamaddalena <dlamaddalena at gmail.com> wrote:
2024 Apr 07
1
NUT v2.8.2, the Easter Egg Edition
A hiccup was reported about validating the tarball signature on some systems, so it was reissued from another workstation. Please don't worry :) Jim Klimov On Tue, Apr 2, 2024, 01:06 Jim Klimov <jimklimov+nut at gmail.com> wrote: > Hello all, > > After a prolonged labour with a few re-issues of the tag and many pushes > during the day, NUT v2.8.2 was found in a strange
2024 Apr 07
1
NUT v2.8.2, the Easter Egg Edition
A hiccup was reported about validating the tarball signature on some systems, so it was reissued from another workstation. Please don't worry :) Jim Klimov On Tue, Apr 2, 2024, 01:06 Jim Klimov <jimklimov+nut at gmail.com> wrote: > Hello all, > > After a prolonged labour with a few re-issues of the tag and many pushes > during the day, NUT v2.8.2 was found in a strange
2022 Mar 11
2
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
2022 Mar 11
2
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
2014 Feb 19
2
snmp-ups shutdowns
On 2014-02-19 03:04, Tim Rice wrote: > If you've got a AP9630 card these notes may be useful. > > # APC ap9630 notes: > # Use firmware 6.0.6 or later if you want SNMPv3 > # Configuration->Shutdown > # In "Start of Shutdown" section, set "Low Battery Duration" and > # "Shutdown Delay" to get enough grace time for the ESXI shutdown > #
2025 Apr 08
1
NUT testing for v2.8.3 (hopefully imminent)
So, NUT v2.8.3-rc1 is out. I first thought it was the release, but some CI runs convinced me otherwise, so there would be a bit of back and forth on the master branch as some recipes get fixed. Apparently, some parallel runs stepped onto each other's toes sometimes, but coinciding the wrong way just once in a few hundred builds. Hopefully I found why and will re-publish in a few hours. Jim