[Nut-upsdev] debugging options on upsdrvctl (was Re: [Nut-upsuser] about Smart-Ups RT)
Arjen de Korte
nut+devel at de-korte.org
Fri May 22 13:54:11 UTC 2009
Citeren Charles Lepple <clepple op 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 following full pathname of
> the driver.
I second both suggestions.
> This wouldn't block the possibility of further debugging of upsdrvctl,
> and it eliminates one more round-trip email to verify where their
> drivers are located (since many packages don't put them in $PATH).
Very true. I'll make some changes to 'upsdrvctl' to print both an
informative message that this is just a wrapper around the drivers and
also make it output the full line that people should run for each
driver that we see in ups.conf.
Best regards, Arjen
Please keep list traffic on the list
More information about the Nut-upsdev