<br><div class="gmail_quote">2009/10/1 Daniel O'Connor <span dir="ltr"><<a href="mailto:doconnor@gsoft.com.au">doconnor@gsoft.com.au</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br></blockquote><div><br>Hi Dan,<br><br>sorry for the lag in answering, but I was off for a week due to some health problems...<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
We have been testing an MGE Pulsar M 3000 and found that the lowbatt<br>
doesn't appear to do much. You can see it in the output of upsc but<br>
battery.charge.low is still the default.<br>
<br>
Setting battery.charge.low with upsrw does seem to 'stick' though so I<br>
we can use that.<br>
<br>
Mostly I'm wondering what the driver param is for :)<br></blockquote></div><br>ooch, right. The param is exposed but not applied.<br>As you told, setting it through upsrw works!<br><br>I've just fixed the param application (subversion r2016), so using "-x lowbatt" or putting it in ups.conf now works as it should.<br>
<br>thanks for the report. I hope you're doing fine.<br><br>cheers,<br>Arnaud<br>-- <br>Linux / Unix Expert R&D - Eaton - <a href="http://www.eaton.com/mgeops">http://www.eaton.com/mgeops</a><br>Network UPS Tools (NUT) Project Leader - <a href="http://www.networkupstools.org/">http://www.networkupstools.org/</a><br>
Debian Developer - <a href="http://www.debian.org">http://www.debian.org</a><br>Free Software Developer - <a href="http://arnaud.quette.free.fr/">http://arnaud.quette.free.fr/</a><br><br>