Re: Uninitialized value in numeric eq (==) after 65 iteration of a loop using fork?!?

Your code is working fine here (ActivePerl 5.8 and Windows XP). I have to agree with ccn : there may be a system limit preventing you from create 99 child processes at once. Could be give us more information about your system limit ?

Kind regards

--
zejames

Comment on Re: Uninitialized value in numeric eq (==) after 65 iteration of a loop using fork?!?

Replies are listed 'Best First'.
Re^2: Uninitialized value in numeric eq (==) after 65 iteration of a loop using fork?!? by doowah2004 (Monk) on Sep 13, 2004 at 14:45 UTC
Apparently that is the problem, I updated the code with die and I get: Can't fork: Resource temporarily unavailable at testfork1.pl line 14. There must be some sort of limit. My system is ActivePerl 5.8.3, Win XP SP2. I am unsure how to check or change the ability of my system to create child processes, but it looks like that might be the problem. It is interesting that I did not run into this with the code that had children creating children? zejames, out of curiousity, what times did you get when running the code? Thanks all for your quick and correct insight to my prob. Cameron	[reply]
Re^3: Uninitialized value in numeric eq (==) after 65 iteration of a loop using fork?!? by zejames (Hermit) on Sep 13, 2004 at 15:03 UTC
In fact, your code did not work on my machine either : I ran it under Perl builder, which provided me no error except that it did not terminate it. Running it on the comment line was more interesting and gave the same result as your. Interesting to see a different behaviour when using Perl Builder or not. So I've got no figure for you ;) -- zejames	[reply]