> I can only suggest to try running
>
> megatec_usb -a <ups_name>
>
> (with some -D options probably) to ensure that it does the same thing as
> upsdrvctl...
>
> The worst thing is that '-D' option of upsdrvctl doesn't actually
> show debug info...

That's by design. Using 'upsdrvctl' implies backgrounding a driver, which
is obviously not what you want when you want it to run in debug mode.
Imagine that you want to change the command line parameters (to raise or
lower the debug level for instance). Finding how to stop the backgrounded
process is a pain then and will sure result in many questions from users
that have no idea how to send such a process a kill signal.

If you're just interested in the debug output, running

    <drivername> -DDDDD -a <upsname>

is not that difficult to remember.

Best regards, Arjen
-- 
Eindhoven - The Netherlands
Key fingerprint - 66 4E 03 2C 9D B5 CB 9B  7A FE 7E C1 EE 88 BC 57


_______________________________________________
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

Reply via email to