search for: lowoverride

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 scenarios where that can be useful - just was surprised to see no apparent...

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 scenarios where that can be useful - just was surprised to see no apparent...

I think it can be useful in a scenario like: - Large UPS, that powers 2 hosts: one is VMServer with just a small boot driver and the second is a NAS with all the disks for the first server. - UPS is connected by USB to another host (such as a small Raspberry PI), acting as the NUT primary. - Both machines served by UPS are NUT secondaries. - The NAS box can only shutdown one the VMware is fully

I think it can be useful in a scenario like: - Large UPS, that powers 2 hosts: one is VMServer with just a small boot driver and the second is a NAS with all the disks for the first server. - UPS is connected by USB to another host (such as a small Raspberry PI), acting as the NUT primary. - Both machines served by UPS are NUT secondaries. - The NAS box can only shutdown one the VMware is fully

Yeah, I have no lack of imagination about scenarios where that can be useful - just was surprised to see no apparent "here's how you do it" sort of man page or something, Although technically the shutdown scenario like yours, where a NAS server only is told to go down - or actually does so (which is substantially different and can be implemented elsewhere) - after its consumers go

Yeah, I have no lack of imagination about scenarios where that can be useful - just was surprised to see no apparent "here's how you do it" sort of man page or something, Although technically the shutdown scenario like yours, where a NAS server only is told to go down - or actually does so (which is substantially different and can be implemented elsewhere) - after its consumers go