<snip> > my theory was that it had something to do with IO::Socket not being totally > thread-safe. i've been meaning to try and remove all of my 'use > IO::Socket::INET' and replace them with either a basic require or > Thread::Use's useit to see if i could delay loading of the module until > after all threads were spawned. i haven't been able to try that yet, but i > suspect that the warnings might go away.
>>> Hi Jack. Thanks for the response. I suppose it is a case of "misery loves company" here. For what it's worth, I don't use the IO::Socket modules. I only use Socket.pm as I've found it more reliable. <snip> > at any rate, it seems to have no effect on program execution. sockets seem > to function normally. i've been running this in production for a while now > and have had no troubles related to this. >>> This is good to know. Thanks...Steve > > jack > >
