Internet is full of recommendations to use SIG ALARM while socket connect, and as far as I remember, socket "Timeout" option was not working right for connection stage (and/or for DNS timeouts). (not sure about current IO::Socket versions, through)
Also SIG ALARM is not affecting socket read/write timeouts happened after alarm(0)
thread being left in a state unable to create further sockets?Need probably to see more code, what happening after/before eval?
In reply to Re^3: Apache Processes Hung on Socket Issue
by vsespb
in thread Apache Processes Hung on Socket Issue
by eallenvii
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |