On Oct 28, 2016, at 8:43 AM, Dorsey, Scott B. (LARC-D316)[LITES II] wrote:
>
> So, no suggestions for diagnosing intermittent driver loading issues?
>
>> You might also benefit from adjusting these variables:
>> http://lists.alioth.debian.org/pipermail/nut-upsuser/2016-October/010352.html
>
>
So, no suggestions for diagnosing intermittent driver loading issues?
> You might also benefit from adjusting these variables:
> http://lists.alioth.debian.org/pipermail/nut-upsuser/2016-October/010352.html
I tried changing the polling interval, it doesn't seem to make any difference.
Either
"lsusb" always shows the UPS. It's always there with an ls -al.
I can start the thing, and it doesn't load wait a minute and try again and
it doesn't load
wait another minute and it loads then try to restart a minute later and it
doesn't load.
> You might also benefit from
> On Oct 12, 2016, at 2:00 PM, Dorsey, Scott B. (LARC-D316)[LITES II]
> wrote:
>
> It does in fact show exactly what you describe. Udev is working properly
> with the device file being assigned to group
> dialout, which the nut user is in. You were correct about my
It does in fact show exactly what you describe. Udev is working properly with
the device file being assigned to group
dialout, which the nut user is in. You were correct about my having had to
install the libusb-devel kit to make 2.7.4
build, but it does build properly and everything seems to
[please use Reply-All - this list does not modify the reply-to header.]
> On Oct 10, 2016, at 8:53 AM, scott.b.dor...@nasa.gov wrote:
>
> I have a user running centos 6.8 with a brand new Tripplite HID (protocol
> 4016)
> UPS. So I installed nut 6.5 from EPEL and it sometimes worked, and it
>
I have a user running centos 6.8 with a brand new Tripplite HID (protocol 4016)
UPS. So I installed nut 6.5 from EPEL and it sometimes worked, and it
sometimes didn't, and it seemed to be very inconsistent about loading the
device driver.
So, looking around and after spending some time
7 matches
Mail list logo