On Nov 19, 2015, at 12:04 PM, Róbert SZAKSZ <[email protected]> wrote: > output(nutdrv_qx cmd upsdrvctl -DDD start) > > Network UPS Tools - UPS driver controller 2.7.3 > 0.000000 > If you're not a NUT core developer, chances are that you're told to enable > debugging > to see why a driver isn't working for you. We're sorry for the confusion, but > this is > the 'upsdrvctl' wrapper, not the driver you're interested in. > > Below you'll find one or more lines starting with 'exec:' followed by an > absolute > path to the driver binary and some command line option. This is what the > driver > starts and you need to copy and paste that line and append the debug flags to > that > line (less the 'exec:' prefix). > > 0.000665 Starting UPS: infosec > 0.000891 1 remaining attempts > 0.001135 exec: /usr/lib/ups/driver/nutdrv_qx -a infosec
The above message is saying that the debug flags need to be added to the driver command line, not to the upsdrvctl command: /usr/lib/ups/driver/nutdrv_qx -DDD -a infosec -- Charles Lepple clepple@gmail _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
