What jethro said: Only fork if you need to do something in both processes.

If that's the case, here is a working example:

#!/usr/bin/env perl

use 5.014;
use strict;
use warnings;

my $pid = fork;

if (!defined $pid) {
    die "Cannot fork: $!";
}
elsif ($pid == 0) {
    # client process
    say "Client starting...";
    sleep 10; # do something useful instead!
    say "Client terminating";
    exit 0;
}
else {
    # parent process
    say "Parent process, waiting for child...";
    # do something useful here!
    waitpid $pid, 0;
}
say "Parent process after child has finished";
[download]

One thing to note is that fork returns undef on failure, and undef == 0 compares as true, so your error handling wouldn't work. To easily test the error case, start a new bash and set ulimit -u $number_of_allowed_processes, then start the perl script.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.