search for: cba1572d

>From my understanding, alone with other NUT behaviors it would not. Even if NUT drivers already do (or are changed to) react to the actual charge/runtime going below this setting to fabricate an LB status, this as a driver setting/override would have immediate effect on all clients like `upsmon` watching the device status on their shared data server. This simultaneously requested shutdown

>From my understanding, alone with other NUT behaviors it would not. Even if NUT drivers already do (or are changed to) react to the actual charge/runtime going below this setting to fabricate an LB status, this as a driver setting/override would have immediate effect on all clients like `upsmon` watching the device status on their shared data server. This simultaneously requested shutdown

Hi Jim, I was thinking about setting different values for each device , so the first system has higher values and shutdowns?earlier:override.battery.charge.lowoverride.battery.runtime.low Won?t it work ? Best Regards,Strahil Nikolov? On Sunday, August 6, 2023, 7:41 PM, Jim Klimov via Nut-upsdev <nut-upsdev at alioth-lists.debian.net> wrote: Yeah, I have no lack of imagination about

Hi Jim, I was thinking about setting different values for each device , so the first system has higher values and shutdowns?earlier:override.battery.charge.lowoverride.battery.runtime.low Won?t it work ? Best Regards,Strahil Nikolov? On Sunday, August 6, 2023, 7:41 PM, Jim Klimov via Nut-upsdev <nut-upsdev at alioth-lists.debian.net> wrote: Yeah, I have no lack of imagination about