Note that I have seen some problems with detecting a USB APC SmartUPS
with both this and the previous version, however, in the past I've also
had it working with the previous version, so I'm not quite sure what's
going on. I think I have seen it working after the libusb update at
p2k11 but not 100% sure.

Unfortunately I don't have available hardware to track this down
further at the moment (the SmartUPS I had problems with is on a remote
system which I can't use for debugging) and it works totally ok with
the USB Liebert I have here..

If anyone can confirm whether they see NUT working with USB smartups
on 2.6.2 on a system with packages dated from sometime in December
that would be a useful data point.. just running "sudo nut-scanner -U"
(without a daemon attached to the relevant ugen device) is enough to
see; it should give output similar to this:

$ sudo nut-scanner -U
Scanning USB bus.
[nutdev1]
        driver = "usbhid-ups"
        port = "auto"
        vendorid = "06DA"
        productid = "FFFF"
        product = "PowerSure Personal XT"
        vendor = "LIEBERT"
        bus = "000"

(this is in the nut-scanner package for 2.6.2 but as noted in the
commit log, is rolled into the main package for 2.6.3).




On 2012/01/11 09:01, Stuart Henderson wrote:
> CVSROOT:      /cvs
> Module name:  ports
> Changes by:   [email protected]   2012/01/11 09:01:33
> 
> Modified files:
>       sysutils/nut   : Makefile distinfo 
>       sysutils/nut/patches: patch-clients_Makefile_in 
>                             patch-drivers_blazer_usb_c 
>                             patch-tools_nut-scanner_nutscan-ip_h 
>       sysutils/nut/pkg: MESSAGE-main PLIST-main 
> Removed files:
>       sysutils/nut/patches: patch-configure 
>       sysutils/nut/pkg: DESCR-scanner PFRAG.shared-main 
>                         PFRAG.shared-scanner PLIST-scanner 
> 
> Log message:
> update to NUT 2.6.3.
> 
> - nut-scanner has been changed to dlopen()ing modules, so roll it into the
> main package now this can be done without bringing in excess dependencies.

Reply via email to