Hm... are you using Barr's IO::Socket library? At the
corporation where I worked we have learned that the IO::Socket
library, although excellent for very light socket work,
has a horrible time dealing with error conditions. It would
appear like error handling was not thoroughly designed into
the infrastrucutre, it feels as if it almost was an afterthought.
My suggestion for you, as amazingly horrible as this might
sound, is attempt to recreate the problem utilizing more
low level socket code (in other words, do the work by hand.)
If however i've been wrong all along, and you aren't useing
the IO::Socket library, then go the other way, and try it :)
Maybe you are forgetting something that needed to be done (an
fflush here, an fflush there, here an fflush, there an fflush,
everywhere an fflush.) Sorry I couldn't be more helpful, but
without more of a description of the problem domain, that's
as close as we are going to get :) | [reply] |
It would be good to know a little bit more about your environment.
For instance, the ISP that hosts one of my websites limits CGI scripts to running for 10 seconds, and a 8MB footprint. Other servers are known to set even more restrictive limits.
Of course, if you're doing this as root on your own local box, then it that changes the whole set of parameters. How much data are you trying to pass?
--Chris | [reply] |