<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">I think it can be useful in a scenario like:<div><br></div><div>- 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. </div><div>- UPS is connected by USB to another host (such as a small Raspberry PI), acting as the NUT primary.</div><div>- Both machines served by UPS are NUT secondaries.</div><div>- The NAS box can only shutdown one the VMware is fully stopped to avoid corruption at several levels.</div><div><br></div><div>If the secondaries can define their one parameters for initiating the shutdown, one can decide something like:</div><div><br></div><div>- VMware will shutdown at 20% battery left OR 15min of runtime left</div><div>- NAS will shutdown at 10% ou 8min left</div><div><br></div><div>Another approach is to attempt to define a way to sync secondaries… but that’s much more complex.</div><div><br></div><div>Arnaldo. <br><div><br><blockquote type="cite"><div>On Aug 6, 2023, at 12:39 PM, Jim Klimov via Nut-upsuser <nut-upsuser@alioth-lists.debian.net> wrote:</div><br class="Apple-interchange-newline"><div><div dir="ltr">Hello all again,<br><div><br> While looking at <a href="https://github.com/networkupstools/nut/issues/2014">https://github.com/networkupstools/nut/issues/2014</a> I understood that I am</div><div>not sure if currently NUT has a standard way of triggering a shutdown based on remaining charge</div><div>or runtime, if a device/driver lacks a `battery.charge.low` setting but has readings for the values</div><div>themselves.</div><div><br></div><div> Such an ability rings a bell to me, but maybe it is specific to some drivers and is not</div><div>something ubiquitous - as being in the driver (and/or upsmon/upssched?) core codebase?</div><div><br></div><div> So there are a few questions stemming from this:</div><div>* Can a user currently (on NUT 2.8.0) set up battery percentage based shutdowns</div><div> when the "low" variable is missing in the driver/device? (Suggestions in the ticket</div><div> linked above are welcome)<br></div><div>* Does it make sense to add something like this (if missing) to be consistent on</div><div> un-capable devices? Or is it already there but too buried in code or docs?</div><div>* Would anyone step up to make this setup easy for newcomers (even if it means "just"<br></div><div> finding a chapter in the docs/FAQ and making it better exposed, perhaps in the Wiki),</div><div> or more so if design and coding are due? ;)</div><div><br></div><div>Jim</div><div><br></div></div>
_______________________________________________<br>Nut-upsuser mailing list<br>Nut-upsuser@alioth-lists.debian.net<br>https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser<br></div></blockquote></div><br></div></body></html>