Re: bad ping status with the forks module

First of all, let me welcome you to Pelmonks erc_fun and thank you for registering. I stand corrected due to the kind admonishments of BrowserUk and I agree with him when he says:

"And going by your demonstration of the failure, the problem appears to clearly lie entirely within, or as a side effect of using the Forks module,..

Howerver I still have to desagree with him as to :

"...and I see no way that re-building perl would have any effect whatsoever."

Obviously there is some difference between your two systems and we still don't know what that difference is.

One thing I noticed, your perl was built with native threads. From your original post:

usethreads=define use5005threads=undef useithreads=define usemultiplicity=define

Which , at best, is redundant to the forks module and, at worst, is colliding with forks and causing your problem. (I can't confirm either way as I can't get the forks module to complete make test on my system.)

Look, I don't know how to fix your system. You have three choices.

Change your code.

Write more tests in hopes of further isolating the problem.

Start swinging a hammer. i.e. rebuild perl, rebuild forks.

To rebuild perl see Install parallel Perl on Debian
To rebuild forks see A Guide to Installing Modules

s//----->\t/;$~="JAPH";s//\r<$~~/;{s|~$~-|-~$~|||s |-$~~|$~~-|||s,<$~~,<~$~,,s,~$~>,$~~>,, $|=1,select$,,$,,$,,1e-1;print;redo}

Comment on Re: bad ping status with the forks module

Replies are listed 'Best First'.
Re^2: bad ping status with the forks module by BrowserUk (Patriarch) on Jul 15, 2006 at 07:23 UTC
starbolin++ 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.	[reply]

Replies are listed 'Best First'.

Re^2: bad ping status with the forks module
by BrowserUk (Patriarch) on Jul 15, 2006 at 07:23 UTC

starbolin++

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.

[reply]