Wow :-) I'll have a read through it.
On Sun, 10 Mar 2024 at 15:54, Roger Price <
roger_at_rogerprice.org_chrib...@duck.com> wrote:
> On Sun, 10 Mar 2024, Alan via Nut-upsuser wrote:
>
> > Very good point. I hope to write a beginners guide -- more like
> adopting my
> > notes --on NUT.
>
> I did
On Sun, 10 Mar 2024, Alan via Nut-upsuser wrote:
Very good point. I hope to write a beginners guide -- more like adopting my
notes --on NUT.
I did the same thing, 131 pages, at
https://rogerprice.org/NUT/ConfigExamples.A5.pdf
Roger___
Nut-upsuser
Very good point. I hope to write a beginners guide -- more like adopting
my notes --on NUT.
I could summarise your point that technically one should only override
settings that NUT can act upon (like those settings that control Low
Battery or, as stated in the documentation if the reported value
Thanks Charles for the clarification.
If NUT cannot control it then removing it would, IMO add value.
On Sun, 10 Mar 2024 at 00:14, Charles Lepple <
clepple_at_gmail.com_chrib...@duck.com> wrote:
> On Mar 9, 2024, at 5:16 PM, chrib...@duck.com wrote:
> >
> > The posting at
> https://github.com/n
On Mar 9, 2024, at 6:14 PM, Charles Lepple wrote:
>
> On Mar 9, 2024, at 5:16 PM, chrib...@duck.com wrote:
>> I used the override.ups.delay.start = -1 in nut.conf and this is now being
>> reported.
The ups.conf man page describes the direction that the data flows with
override.*:
> Use with c
On Mar 9, 2024, at 5:16 PM, chrib...@duck.com wrote:
>
> The posting at
> https://github.com/networkupstools/nut/issues/432#issuecomment-405371395
> references ups.delay.start and suggests setting it to -1.
>
> upsrw -l pve1@localhost listed this as modifiable but any attempt at
> modifying th
Hi Charles,
The posting at
https://github.com/networkupstools/nut/issues/432#issuecomment-405371395
references ups.delay.start and suggests setting it to -1.
upsrw -l pve1@localhost listed this as modifiable but any attempt at
modifying the value failed. I used the *override.ups.delay.start = -1
On Mar 8, 2024, at 7:07 AM, Roger Price wrote:
>
> Perhaps setting lowbatt = 50 in ups.conf would help.
Roger, good point.
That option is missing in the usbhid-ups man page, so I logged an issue to
remind us to fix that: https://github.com/networkupstools/nut/issues/2356
Since I am used to fi
On Mon, 4 Mar 2024, Alan C. Bonnici via Nut-upsuser wrote:
Platform: Proxmox VE 8.1.4
NUT version: Network UPS Tools upsstats 2.8.0
I configured Proxmox and I can pull up the UPS stats.
Typing in `upsrw -l cyberpower@localhost` I get the following:
[battery.charge.low]
Remaining battery level
On Mar 4, 2024, at 3:23 PM, Alan C. Bonnici via Nut-upsuser
wrote:
>
> I would like to push up the shutdown process to initiate when the ups is at
> 50% rather than 10% mainly because there is a need to down other servers.
>
Some UPSes have a limited range for adjusting the LB threshold, or d
*Platform: Proxmox VE 8.1.4NUT version: Network UPS Tools upsstats 2.8.0*
I configured Proxmox and I can pull up the UPS stats.
Typing in `*upsrw -l cyberpower@localhost*` I get the following:
*[battery.charge.low]Remaining battery level when UPS switches to LB
11 matches
Mail list logo
