The probable reason it works on windows and not linux is that fork under windows is really just a thread, so the "forked child" is actually still a part of the same process, (which according to anonymonk above is important to ssl connections?).
That suggests a possible way forward would be to use threads rather than fork, which would (might) get around the problem on both platforms. Of course, it might create others.
In reply to Re^3: IO::Socket::SSL + fork problem
by BrowserUk
in thread IO::Socket::SSL + fork problem
by mrhyde
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |