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,
I would like to confirm my understanding of how NUT operates in a Master /
Server environment. Some areas are not clear.
1 Power fails
2. Nut Master polls the UPS according to *POLLFREQ (in seconds)* setting in
*upsmon.conf*.
2.1 When *battery.runtime.low (in seconds)* or *battery.charge
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
