<br><br><div class="gmail_quote">2009/9/2 Markus Wildi <span dir="ltr"><<a href="mailto:wildi.markus@bluewin.ch">wildi.markus@bluewin.ch</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;">
Hello<br>
<br>
I recently switched from apcupsd to NUT2.2.2 without<br>
any troubles.<br>
<br>
I tried to figure out how I can configure the self-test<br>
intervall. The command upsrw lists only the variables<br>
<br>
battery.charge.low<br>
battery.runtime.low<br>
ups.delay.shutdown<br>
ups.delay.start<br>
<br>
The command usbhid-ups -D and the listing under<br>
<br>
<a href="http://obsvermes.org/cgi-bin/nut/upsstats.cgi?host=apcsmart@localhost&treemode" target="_blank">http://obsvermes.org/cgi-bin/nut/upsstats.cgi?host=apcsmart@localhost&treemode</a><br>
<br>
show no hint on appropriate variable.<br>
<br>
I scanned to log files and found no hint on successfull self-test.<br>
</blockquote><div><br>it seems APC doesn't support this, or at least we have nothing mapped for this.<br>for example, on Eaton / MGE units, we have "UPS.BatterySystem.Battery.TestPeriod" mapped to "ups.test.interval"<br>
<br>to validate this, please upgrade to a more recent version (ie 2.4.1) and post back the output of usbhid-ups -D</div></div><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>