Gentlemen, I am making progress with with my APC USB device. However, I have encountered a problem with the current build for newhidups. The problem is that on my system libusb.so resides in /usr/lib, which at the end of the shutdown sequence is no longer available. I believe that this is probably a relatively generic problem, and I think that the proper solution is to link all usb drivers statically if libusb.so does not reside in /lib. Could someone more familiar with the configure and build process please provide me with an appropriate change? Thank you, AG -- ---------------------------------------------------------------------- Alfred Ganz alfred-ganz@agci.com AG Consulting, Inc. (203) 624-9667 440 Prospect Street # 11 New Haven, CT 06511 ----------------------------------------------------------------------
arnaud.quette@mgeups.com
2005-Jul-28 09:01 UTC
[Nut-upsdev] Re: problem with dynamic libusb.so
> I am making progress with with my APC USB device. However, I have > encountered a problem with the current build for newhidups. > > The problem is that on my system libusb.so resides in /usr/lib, which > at the end of the shutdown sequence is no longer available. I believe > that this is probably a relatively generic problem, and I think that the > proper solution is to link all usb drivers statically if libusb.so does > not reside in /lib. > > Could someone more familiar with the configure and build process please > provide me with an appropriate change?the solution I've applied on Debian is to ask libusb packagers to install libusb on /lib so that it's reachable, in particular in shutdown for powerfail situation... The static link solution is not suitable. Finally note that this kind of issue will be adressed by the NUT Packaging Standard tasks. If not already done, bug your distribution's libusb package so that it's installed on the root fs. Arnaud