On Sun, 2 Jun 2024, chribonn at duck.com wrote:> ? # if the charge is less than 75 percent trigger a LB status > ? override.battery.charge.low = 75 > ? # if the remaining charge is less than 1200s (20 minutes) trigger a low battery status > ? override.battery.runtime.low = 1200 > ? # wait 5 minutes for ups to power off > ? override.ups.delay.shutdown = 300 > ? # Could offdelay act as an ovverride for override.ups.delay.shutdown? > ? offdelay = 300> Is the comment about offdelay?(in red) correct / can this line be eliminated?.??My understanding is "yes", but others may have deeper knowledge. In general you don't need any "override" variables. See the comment about override.<variable> at https://networkupstools.org/docs/man/ups.conf.html> Can the UPS automatically come online one the ondelay passes -- I presume this > can vary with the UPS brand and NUT driver.The UPS will be online and recharging once wall power returns, but will not feed power to the server until ondelay passes.> ---------------------------------------------- My goal is to tell a story of > how Proxmox with Windows Guests can be configured with NUT so that if there is > a power failure. I hope to design this such that others can add alternative > methods and update HowTo modules for each step.> I feel I am at the tail end of a long long learning curve and would like to > document the story of how one should go aboNot only will this be useful as your own documentation, but also useful for many others. Roger
On Jun 2, 2024, at 12:14?PM, Roger Price wrote:> >> Is the comment about offdelay (in red) correct / can this line be eliminated?. > > My understanding is "yes", but others may have deeper knowledge.I don't have a ton of direct experience with this post-v2.7.4, but someone else wrote this up for overriding battery.charge.low: https://alioth-lists.debian.net/pipermail/nut-upsuser/2023-November/013481.html (There are a few other override/ignorelb write-ups in the list archives, too. Unfortunately, DDG is not finding them and I just snagged the first hit on Google.) The key is that any override.* variables without "ignorelb" are just telling white lies to any clients connected to upsd, without any corresponding change in behavior in the driver or UPS. With "ignorelb", you are telling the driver to ignore the UPS-calculated LB signal, and synthesize it using the override.* parameters. So I would either: 1) use offdelay and don't use override.battery.runtime.low 2) use ignorelb and remove offdelay I am skeptical that a Phoenixtec-based UPS has fully configurable shutdown thresholds, but that is probably based on very old information, and I would love to be proven wrong..