in reply to Re^2: launching concurrent processes
in thread launching concurrent processes
When fork() is called, you end up having two processes: the parent and the child. They both execute the same code (your Perl script), but you can understand if you're in the child testing whether the call returned 0. Then, you're supposed to call exec() (if you really need it) passing the control to the process you want to execute, but this isn't necessary if the code is in the parent script!
The two processes created by fork() are independent, so they will be both running after the call, if this is what you're worried about. Unlike system(), which waits for the child process to complete, after fork() you can do whatever you want in the parent process, even calling fork() two more times to complete the creation of your three subprocesses.
Simple snippet:
which yelds, for example#!/usr/bin/perl use strict; use warnings; sub child { print("Hey, I'm child $$\n"); sleep(2 + rand(5)); print("$$ exiting...\n"); exit(0); } foreach (1 .. 3) { my $pid = fork; die "fork(): $@, stopped" unless defined($pid); child() unless $pid; } # Only the parent reaches this point wait foreach (1 .. 3);
Hey, I'm child 1048 Hey, I'm child 1368 Hey, I'm child 424 1368 exiting... 424 exiting... 1048 exiting...
Flavio
Don't fool yourself.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^4: launching concurrent processes
by Anonymous Monk on Mar 30, 2005 at 16:10 UTC | |
by polettix (Vicar) on Mar 30, 2005 at 16:20 UTC | |
|
Re^4: launching concurrent processes
by Anonymous Monk on Mar 30, 2005 at 16:25 UTC |