Both of these examples are fine for stuff that doesn't do any calls to system or exec.

But that's probably exactly what he wanted to do.
The quick answer is: Read perlipc and go on from there.

Long answer: working on that ;-)

Update: Here's the long answer:

#!/usr/bin/env perl

use strict;
use warnings;
use POSIX qw/:sys_wait_h/;

my $child_pid = undef;

my $status = fork;
die "failed to fork\n" unless defined $status;

if ($status > 0) {
  # this is the parent process.
  local $SIG{ALRM} = sub { print STDERR "operation timed out for PID $
+status\n"; kill 9, $status };
  alarm 10;
  my $pid = 0;
  do {
    $pid = POSIX::waitpid ($status, POSIX::WNOHANG);
  } until ($pid > 0);
  alarm 0;
} else {
  # this is the child process.
  system "ssh a_server_could_hang";
}
[download]

For any non-portability hit your OS vendor :-(

Kay

---

---

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.