Caution when experimenting with this. It's a very effective fork bomb for slightly larger values of 10.

Perl fork behaves exactly like unistd.h fork(), except that the return value differs on failure. When fork fails, it returns undef instead of -1, as C fork() does.

Here's my forking idiom: 

my %kid;
{
    defined(my $cpid = fork) or warn $! and last;
    $cpid and $kid{$cpid} = undef, last;
    undef %kid;          # in child now
    # do childish things
    exit 0;
}
# . . .
delete $kid{wait()} while %kid;

[download]
There are other ways to avoid zombie kids. Which you choose depends on how your program flow is intended to go.

After Compline,
Zaxo

In reply to Re: strange behaviour when forking lots of times by Zaxo
in thread strange behaviour when forking lots of times by jesuashok

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.