> 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.... /var/run/devd.pid /var/run/syslog.pid /var/run/mountd.pid /var/run/istgt.pid /var/run/upslog.pid /var/run/upsmon.pid /var/run/powerd.pid /var/run/samba4/nmbd.pid /var/run/samba4/smbd.pid /var/run/samba4/winbindd.pid /var/run/sshd.pid /var/run/cron.pid /var/run/rsyncd.pid /var/run/lighttpd.pid /var/run/spindown.pid /var/run/upsd.pid /var/run/usbhid-ups-upstl1300.pid Sent from Mail for Windows 10 From: Charles Lepple Sent: Tuesday, August 18, 2015 4:35 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 3:28 PM, Johnny Wong <e430ben...@yahoo.com> wrote: > > So when the UPS is communicating with the driver... it seems to work. > Problem is now that it keeps disconnecting. 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. > Any recommendation on how to keep the drivers from disconnecting using the > usb_set_altinterface? (PS. Is there a specific value to use?) >From the earlier usbconfig output, I only see "bAlternateSetting = 0x0000". >Adding that option (as you did just now) defaults to a parameter of zero. I >will look into this. FYI, some history is here: https://github.com/networkupstools/nut/issues/138 -- Charles Lepple clepple@gmail --- This email has been checked for viruses by Avast antivirus software. http://www.avast.com
_______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
