<br><br><div class="gmail_quote">2009/5/16 Arjen de Korte <span dir="ltr"><<a href="mailto:nut%2Bdevel@de-korte.org">nut+devel@de-korte.org</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;">
Citeren Charles Lepple <<a href="mailto:clepple@gmail.com" target="_blank">clepple@gmail.com</a>>:<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I'm btw wondering if we should pass the debug flags to the driver in  such a case...<br>
comments?<br>
</blockquote>
<br>
Agreed - we have been telling people to "use upsdrvctl" and "enable  debugging", and the two messages conflict with each other somewhat.<br>
</blockquote>
<br></div>
I'm slightly worried about you and Arnaud not recalling why this isn't a good idea:<br>
<br>
  <a href="http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-May/002712.html" target="_blank">http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-May/002712.html</a><br>
<br>
Also, if multiple drivers are configured in ups.conf, it probably would lead to an endless mess of debugging output.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
There isn't much to debug in upsdrvctl anyway.<br>
</blockquote>
<br></div>
Maybe, although passing on the debug flags to drivers would effectively remove the possibility to debug upsdrvctl once and for all. I for certain wouldn't like that, because in the past I have used this quite often.<br>
<br>
Don't forget that the debugging options in NUT aren't meant to help Joe User, it's to enable us (the developers) to get additional information on why something isn't working as it should. Therefor, when asking Joe to enable debugging, we should make it abundently clear what we want from him. So don't tell him to 'enable debugging', but post the commandline to execute on his system.<br>
</blockquote></div><br>you're right, Arjen.<br>thanks for recalling us that ;-)<br><br clear="all">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>