I think the answer by
sauoq will most likely be the right one.
I just wanted to chime in with something else. Your code is assuming that fork() always succeeds (a dangerous assumption). Remember that it will return undef upon failure. A failure can be triggered by many events outside of your control, so you should be prepared to deal with them gracefully.
I offer you this substitute code instead:
use strict;
use warnings;
use constant FORK_WAIT => 2;
use constant MAX_ATTEMPTS => 10;
our $attempt = 0;
my $pid = undef;
while (not defined ($pid = fork())) {
die "Too many failed fork() attempts: $!\n"
if ++$attempt > MAX_ATTEMPTS;
warn "fork() failed: $!\n";
sleep $FORK_WAIT;
}
if ($pid) {
# I'm the father
} else {
# I'm the son
}
Hope this helps,
Edit: Thanks to wtp for the correction in the Perl's fork() behavior.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.