You were right, there was 2 process running.  

What I did was kill both the usbhid-ups processes and reloaded the drivers 
again.  Which still took about 10 tries before it would see the UPS.

Once it was loaded, same thing.  It would disconnect and connect 

Sent from Mail for Windows 10



From: Charles Lepple
Sent: Tuesday, August 18, 2015 6:37 PM
To: Johnny Wong
Cc: nut-upsuser@lists.alioth.debian.org
Subject: Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3


On Aug 18, 2015, at 9:07 PM, Johnny Wong <e430ben...@yahoo.com> wrote:
> 
>> Is it possible that there is another copy of the driver running in the 
>> background? There is apparently an issue where we only write a PID file when 
>> the driver goes into the background, and "-D" prevents that.
>  
> I don't see another usbhid-ups running ... unless its "hidden"....  I would 
> have to install the unhide package then....
> 

What I mean is that you can't have more than one usbhid-ups process talking to 
the same UPS at one time - regardless of whether they write a PID file. In the 
case of running with "-D", you would need to double-check for any in the 
background (and there was a PID file named usbhid-ups-upstl1300.pid). "ps 
auxww|grep [u]sbhid-ups" should show only one driver in either case.

Still looking into the altsetting issue. I would have to shuffle a few machines 
around to get a copy of 10.2 running on a box that isn't being actively used 
for anything else, but maybe there is something in their source control logs.

-- 
Charles Lepple
clepple@gmail





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

Reply via email to