I have a script that does tape backups. It forks a child process for each tape device on the host so that multiple tape devices are written concurrently rather than consecutively. This is the skeleton of the process, which uses pipes so that the children can log messages that the parent can read later.
use IO::Pipe;
...
foreach $tapeDevice (@tapeDevices)
{
$pipeFH = IO::Pipe->new();
...
if($pid = fork())
{
# This is the parent.
$pipeFH->reader();
push @pipes, $pipeFH;
...
}
elsif(defined $pid)
{
# This is the child.
$pipeFH->writer();
# Do lots of stuff writing to tape
...
$pipeFH->print("some message or other");
...
}
else
{
# Fork failed for some reason.
die "fork: $!\n";
}
}
# We have now forked a child for each tape device so
# wait for our children to finish. Print exit status.
while((my $returnPID = wait()) != -1)
{
print "Child $returnPID returned status ",
$? >> 8, "\n";
}
# All children have returned, get messages.
foreach $pipe (@pipes)
{
while(defined($_ = $pipe->getline()))
{
# Do something
...
}
}
That is the bare bones of the mechanism. I have not attempted to reconcile use strict; and my or our here as it is just an illustration. I hope this is useful. Cheers, JohnGG
-
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.
|