[Nut-upsdev] debugging options on upsdrvctl (was Re: [Nut-upsuser] about Smart-Ups RT)

Arjen de Korte nut+devel at de-korte.org
Sat May 16 09:05:15 UTC 2009

Citeren Charles Lepple <clepple op 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:


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

More information about the Nut-upsdev mailing list