On Aug 22, 2018, at 2:03 PM, Valentin Merkulov <[email protected]> wrote: > > With interruptonly the driver output goes into a loop (is it an > expected behavior?)
Yes, this is what the driver does in the background if you do not pass any "-D" flags. If you were to start `upsd` at that point, it should be able to provide data to clients like `upsc`. However, since you needed to pass `-u root` to the driver, you may need to pass `-u root` to `upsd` as well. > After I interrupt the loop and launch the driver > again, it would return "No matching HID device found" until I unplug / > re-plug USB cable. I am not sure which component is at fault: NUT for not resetting something (though the automatic close-on-exit behavior in the OS should take care of this - or at least, it has in every other case I am aware of), libusb or FreeBSD for not cleaning up, or the UPS for not recovering properly. Issue logged: https://github.com/networkupstools/nut/issues/600 _______________________________________________ Nut-upsuser mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
