Many thanks for that; I seem to be getting somewhere :-):<br><br>----------------<br>[root@www www]# /sbin/upsdrvctl -DD -u root start<br>Network UPS Tools - UPS driver controller 2.2.0-<br>Starting UPS: myups<br>exec: /sbin/megatec_usb -a myups
<br>Network UPS Tools 2.2.0- - Megatec protocol driver 1.5.4 [megatec_usb]<br>Carlos Rodrigues (c) 2003-2007<br><br>Serial-over-USB transport layer for Megatec protocol driver [megatec_usb]<br><br>Megatec protocol UPS detected [UNITEK Alph1200Sx A1].
<br>-----------------<br>The driver seems to load fine from the above, however upsd now seems a no-go:<br>[root@www ups]# /usr/sbin/upsd<br>Network UPS Tools upsd 2.2.0-<br>not listening on <a href="http://0.0.0.0">0.0.0.0
</a> port 3493<br>------------------<br>If I try:<br>[root@www ups]# /usr/bin/upsc myups@localhost ups.status<br>Error: Driver not connected<br><br>I also discovered that the log file is getting filled up with these errors:
<br><br>---------------------<br>Jan 2 22:38:19 www kernel: usb 1-2: usbfs: process 24538 (megatec_usb) did not claim interface 0 before use<br>Jan 2 22:38:19 www kernel: usb 1-2: usbfs: process 24538 (megatec_usb) did not claim interface 0 before use
<br>Jan 2 22:38:20 www upsmon[24650]: Poll UPS [myups@localhost] failed - Driver not connected<br>Jan 2 22:38:20 www kernel: usb 1-2: usbfs: process 24380 (megatec_usb) did not claim interface 0 before use<br>Jan 2 22:38:20 www kernel: usb 1-2: usbfs: process 24380 (megatec_usb) did not claim interface 0 before use
<br>Jan 2 22:38:21 www kernel: usb 1-2: usbfs: process 24538 (megatec_usb) did not claim interface 0 before use<br>Jan 2 22:38:21 www kernel: usb 1-2: usbfs: process 24538 (megatec_usb) did not claim interface 0 before use
<br>Jan 2 22:38:22 www kernel: usb 1-2: usbfs: process 24380 (megatec_usb) did not claim interface 0 before use<br>Jan 2 22:38:22 www kernel: usb 1-2: usbfs: process 24380 (megatec_usb) did not claim interface 0 before use
<br>-------------------------------<br><br>Same thing happens if I use the init script for everything (I added the -u root to the script).<br><br>Thanks,<br>Joe<br><br><div class="gmail_quote">On Jan 2, 2008 8:54 PM, Arjen de Korte <
<a href="mailto:nut+users@de-korte.org">nut+users@de-korte.org</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">
Joseph Borg wrote:<br><br>> The strange thing is that this fails really fast...it's as though it's<br>> not even trying to detect the ups....<br><br></div>No, it won't. You need to pass the '-u root' option, since the
<br>hotplug/udev rules are not setup for this VID:PID combination. Until<br>then, you'll have to tell the driver to run as root, otherwise it will<br>drop privileges and will never be able to claim the port.<br><br>Best regards, Arjen
<br></blockquote></div><br>