search for: protoocl

...charge > (as in, "possibly harmful to the chemistry of the cells")? Or an > euphemism(*) for being "well charged" (maybe not 100% if the device hovers > at some 85%-95% to extend battery life)? I don't think we should use .high, unless a significant number of units/protoocls issue a "battery charge is high" state with a consistent meaning. So no. If this is about having variables with thresholds that control devices or cause synthetic setting of some variable (like turning on LB if charge% is < battery.charge.low), then it makes sense. If there is no...

Hello all, During discussion at https://github.com/networkupstools/nut/pull/2430#discussion_r1592317940 I found that while `nut-names.txt` documents the `battery.charge.low` as the "Remaining battery level when UPS switches to LB (percent)", there is no counterpart as `battery.charge.high`. First I thought one could be just added... but for that matter, what could one logically mean -

https://bugzilla.samba.org/show_bug.cgi?id=5403 Summary: -H (--hard-links) is broken when sending to remote Product: rsync Version: 3.0.2 Platform: x86 OS/Version: NetBSD Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: gcw@pobox.com

...sibly harmful to the chemistry of the cells")? Or an > > euphemism(*) for being "well charged" (maybe not 100% if the device > hovers > > at some 85%-95% to extend battery life)? > > I don't think we should use .high, unless a significant number of > units/protoocls issue a "battery charge is high" state with a consistent > meaning. So no. > > If this is about having variables with thresholds that control devices > or cause synthetic setting of some variable (like turning on LB if > charge% is < battery.charge.low), then it makes...