Citeren Charles Lepple clep...@gmail.com:
I concede that debugging output from multiple drivers would be a mess,
but it wouldn't hurt to have debug level 1 or 2 print a message saying
that they should 1) go to the nut-upsdev list for further guidance,
and 2) when they ask for help, include the
On Sat, May 16, 2009 at 5:05 AM, Arjen de Korte nut+de...@de-korte.org wrote:
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
2009/5/16 Arjen de Korte nut+de...@de-korte.org nut%2bde...@de-korte.org
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,
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
On May 15, 2009, at 5:16 PM, Arnaud Quette wrote:
2009/5/15 dblackbeer dblackb...@gmail.com
...
here's error message:
[r...@dgc etc]# ../bin/upsdrvctl -D -u nut start
I really meant the *driver*, not upsdrvctl: ../bin/apcsmart -D -
a apcsmart
I'm btw wondering if we should pass
