Re^2: bad ping status with the forks module

However I still have to desagree with BrowserUk as to :

That's the problem with coming in half way through a thread and not fully reading back to the beginning--you (I) am apt to miss things.

You are right. If the machine had a non-threaded perl installed prior to the crash, (and if the The same little program works with the forks module on another server., is running a non-threaded version of perl), then that would be a good clue as to a conflict between Forks and threaded perl builds. Acquiring/building a non-threaded build of perl may well restore the function of the program.

I think using threads, or Net::Ping 'syn' mode is a better solution long term, but that's a personal choice.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

Comment on Re^2: bad ping status with the forks module