Hi McA,
I had a developer colleague of mine help me on writing below fork code (after following your advice).
#!/usr/bin/perl -w
use strict;
use POSIX;
my @list=("server1","server2","server3","server4","server5","server6",
+"server7","server8");
my $count = 0;
my $pcount = 5;
foreach (@list)
{
chomp ;
my $real_host = $_;
if( (my $pid = fork()) == 0)
{
print "Processing - $_ \n";
my $wait=ceil(rand(10));
print "Wait:$wait \n";
sleep($wait);
print "Exit Status= $? \n";
if($? ==0)
{
print "$_ Exit successfully \n";
}
else
{
print "$_ Does not Exit successfully \n";
}
print "Completing - $_ \n";
exit;
}
$count++;
while($count >= $pcount)
{
wait();
$count--;
}
}
while(wait() != -1){}
I still don’t understand few parts of this code but I am OK with that. This test code is working perfectly. So I am planning to use the same logic in my orchestrator.
Many thanks for your help.
-
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.
|