comment on

If you really don't care about the process returning just set $SIG{CHLD} = 'IGNORE' and ignore the issue of reaping all together. The other option is to do a NON blocking call to waitpid.

use POSIX qw(:sys_wait_h);

sub REAPER {
   while ((my $pid = waitpid(-1,WNOHANG)) > 0) {
        # do something with $pid;
   }
    $SIG{CHLD} = \&REAPER;
}

$SIG{CHLD} = \&REAPER;
[download]

Then you don't have to worry about your code blocking while waiting for children to return. However this doesn't mean you should do something like.

sub fork_bomb {
   while (1){
      fork_a_kid();
   }
}
[download]

Speaking as a system administrator this won't earn you alot of good sysadmin karma. It is ok to fork many children just remember to limit the number of children on the system at any one time. Please read perlipc and perlfork they helped me out big time.

In reply to Re: fork()ing a large process by Dogma
in thread fork()ing a large process by Jonathan

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Don't ask to ask, just ask
	PerlMonks