Citeren Charles Lepple <clep...@gmail.com>:
I'm btw wondering if we should pass the debug flags to the driver
in such a case...
comments?
Agreed - we have been telling people to "use upsdrvctl" and "enable
debugging", and the two messages conflict with each other somewhat.
I'm slightly worried about you and Arnaud not recalling why this isn't
a good idea:
http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-May/002712.html
Also, if multiple drivers are configured in ups.conf, it probably
would lead to an endless mess of debugging output.
There isn't much to debug in upsdrvctl anyway.
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.
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.
Best regards, Arjen
--
Please keep list traffic on the list
_______________________________________________
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
