Charles Lepple

I want to get the next release out before spending time on this, but I do think that it is worth overhauling the README so that it renders as AsciiDoc...

I’m not in front of a computer at the moment, but the WIP was probably referring to me not wanting to break the Asciidoc website- I was mainly pushing that...

Stepping back, what is systemd trying to accomplish by watching the PID? If the intent is to restart upsmon if it is killed, then the right thing might be to...

@bcl this seems to be motherboard-dependent: http://article.gmane.org/gmane.comp.monitoring.nut.user/9465 What kind of hardware are you running on? Any luck with moving to non-USB3 ports? Also what kernel and libusb does F21 provide?

> Interesting, I'm not sure what it was plugged into, I'll try switching it. The motherboard is an ASRock B85M-ITX > > A quick Google search didn't turn up any...

Thanks, that's a useful data point. It points towards an incompatibility with the newer USB host controllers.

A lot has changed at once, but I have a positive datapoint for more reliable SMART1500LCDT support: - Ubuntu 16.04 (x86_64) - Kernel 4.4.0-38-generic - libusb 1.0.20 (dpkg says "2:1.0.20-1")...

> Could repeated abuse of the TCP API cause problems somehow? The TCP protocol fetches data from the dstate layer. The polling loop proceeds independently of the dstate queries (unless...

The libusb-1.0 branch (#300) is now available in this PPA: https://launchpad.net/~clepple/+archive/ubuntu/nut

> I also found that libusb-1.0 would only work when the UPS was plugged into a USB 2.0 port. @robbiet480 can you elaborate on this? Failure to detect, or disconnects...