[Nut-upsuser] usbhid-ups looping and unresponsive after update
Arjen de Korte
nut+users at de-korte.org
Thu Feb 7 07:24:13 UTC 2008
> The previous driver would stop by typing a CTRL-C when
> running interactively in debug mode. The new driver will not
> respond to a CTRL-C. It does not respond to a "kill -1",
> "kill -2" or a "kill -15" either (Which may or may not be
> OK).
It *will* respond to CTRL-C, but due to the increased debug output, it
behaves very sluggish, so you may need to try a couple of times before it
gets it.
Best regards, Arjen
More information about the Nut-upsuser
mailing list