search for: upscli_tryconnect

...blocking "connect" function. So the nut-scanner is blocked while waiting for the TCP timeout when trying to connect to an IP without upsd available . Since this timeout may be rather long (3 minutes on my host), I would like to add a timeout parameter to upscli_connect. I propose to add a upscli_tryconnect function accepting a timeout parameter, which will be the copy of the current upscli_connect + the management of the timeout. The upscli_connect will be only a wrapper on top of upscli_tryconnect, calling it without timeout. Please let me know if this makes sense to you. See a diff in attachment....

...evelopment code: yes enable libwrap (tcp-wrappers) support: yes build CGI programs: no enable HAL support: no build and install documentation: no build and install the development files: no ........ decided to upgrade to 2.6.2, but failed compile: ./.libs/libnutscan.so: undefined reference to `upscli_tryconnect' collect2: ld returned 1 exit status This built on Slackware 13.1 config.log (not attached due its size) is available at http://members.ausics.net/noelb/nut.config.log Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/...

...r-nut-scanner.o libnutscan.la -lpthread > libtool: link: gcc -I../../clients -I../../include -g -O2 -Wall > -Wsign-compare -o .libs/nut-scanner nut_scanner-nut-scanner.o > ./.libs/libnutscan.so -lpthread -Wl,-rpath -Wl,/usr/local/ups/lib > ./.libs/libnutscan.so: undefined reference to `upscli_tryconnect' > collect2: ld returned 1 exit status > make[3]: *** [nut-scanner] Error 1 > make[3]: Leaving directory `/home/cade/bad/nut-2.6.3/tools/nut-scanner' > make[2]: *** [all] Error 2 > =========================================================================== > > OS is Sla...

Jim Klimov via Nut-upsuser writes: > So... determining that FD is to be reaped proved hard. Internet lore suggests > fcntl() and poll() on the FD, but it just seems valid to them. The errno is > also usually not raised (once I saw a "111: Connection refused" though). > So the best dumb idea so far is to bail out if we spent the whole loop (128 > attempts) and only