, 2003 7:24 PM
To: Perl Perl
Subject: Re: Timing several processes
On Dec 3, 2003, at 10:49 AM, Akens, Anthony wrote:
[..]
print Running vmstat\n;
defined(my $vmstat_pid = fork) or die Cannot fork: $!; unless
($vmstat_pid) {
exec vmstat 5 5 /log/monitor/delta/vmstat.out;
die cannot exec
Hi all!
I'm wanting to write a simple web-based tool to see the status
of several servers at a glance. I know there are many solutions
existing, but I can't learn as much about perl by just using one
of those as I can by writing my own. The first step I want to do
is call a script from cron
It was Wednesday, December 03, 2003 when Akens, Anthony took the soap box, saying:
: Hi all!
:
: I'm wanting to write a simple web-based tool to see the status
: of several servers at a glance. I know there are many solutions
: existing, but I can't learn as much about perl by just using one
:
http://poe.perl.org
Maybe this would be a good job for POE?
-Tom Kinzer
-Original Message-
From: Akens, Anthony [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 03, 2003 7:49 AM
To: [EMAIL PROTECTED]
Subject: Timing several processes
Hi all!
I'm wanting to write a simple web
of is how to tell if all forked processes
have completed before moving on.
-Tony
-Original Message-
From: Tom Kinzer [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 03, 2003 12:35 PM
To: [EMAIL PROTECTED]
Subject: RE: Timing several processes
http://poe.perl.org
Maybe this would
).
-Tony
-Original Message-
From: Akens, Anthony
Sent: Wednesday, December 03, 2003 12:58 PM
To: Tom Kinzer; [EMAIL PROTECTED]
Subject: RE: Timing several processes
I already have some ideas for how I want to build the page, how
to parse the data I will generate, etc.
As I said, I've
of is how to tell if all forked processes
have completed before moving on.
-Tony
-Original Message-
From: Tom Kinzer [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 03, 2003 12:35 PM
To: [EMAIL PROTECTED]
Subject: RE: Timing several processes
http://poe.perl.org
Maybe this would
this has very little to do with terminating a child at a
certain time...
-Tom Kinzer
-Original Message-
From: Akens, Anthony [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 03, 2003 10:07 AM
To: Akens, Anthony; Tom Kinzer; [EMAIL PROTECTED]
Subject: RE: Timing several processes
.
The only bit I'm not sure of is how to tell if all forked processes
have completed before moving on.
-Tony
-Original Message-
From: Tom Kinzer [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 03, 2003 12:35 PM
To: [EMAIL PROTECTED]
Subject: RE: Timing several processes
http
, 0);
print done!\n;
-Original Message-
From: Wiggins d Anconia [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 03, 2003 1:31 PM
To: Akens, Anthony; Tom Kinzer; [EMAIL PROTECTED]
Subject: RE: Timing several processes
I was going to suggest POE as well, 'til I saw that little word
03, 2003 1:50 PM
To: Wiggins d Anconia; Tom Kinzer; [EMAIL PROTECTED]
Subject: RE: Timing several processes
Here's the sample code I'm trying... In essence I would expect to see
The following output:
Running vmstat
Running sar
Waiting... (at this point a long wait while sar and vmstat finish
On Dec 3, 2003, at 10:49 AM, Akens, Anthony wrote:
[..]
print Running vmstat\n;
defined(my $vmstat_pid = fork) or die Cannot fork: $!;
unless ($vmstat_pid) {
exec vmstat 5 5 /log/monitor/delta/vmstat.out;
die cannot exec vmstat: $!;
}
print Running sar\n;
defined(my $sar_pid = fork) or die
drieux wrote:
So while you are in the process of learning
fork() and exec() why not think a bit more
agressively and go with say a pipe to pass
back the information so as not to buy
the IO overhead of writing to files?
While the following was written for a command
line 'let us get
On Dec 3, 2003, at 5:01 PM, Wiggins d'Anconia wrote:
[..]
it might be a framework you could rip off
and use:
http://www.wetware.com/drieux/pbl/Sys/gen_sym_big_dog.txt
Have we come back to POE? POE.
;-)
who knows, after a bit of work the OP may decide that
the 400m of downloadable free software
14 matches
Mail list logo
