I only can give you some ideas I had, when I read your post. First, doing while(1) is just asking for cpu trouble. Second, if you need to get subsecond resolution, you will need another approach.
Maybe POE has an example to do this simple task?
I don't know how pslist outputs. But if it has a mode to give continuous output, like top, maybe you could set up a filehandle read on it, so you would only have to open it once( you may need to rewind the filehandle ). Then you could use IO::Select on it when it was readable.
Here is a simple idea using IPC::Open3. This uses relatively little cpu, at .1 second.
#!/usr/bin/perl
use warnings;
use strict;
use IPC::Open3;
my $pid = shift || $$;
my $pid1 = open3(\*WRITE,\*READ,0,"/bin/sh");
#if \*ERROR is false, STDERR is sent to STDOUT
while(1){
print WRITE "ps -o rss= -p $pid\n";
select(undef,undef,undef,.1);
my $size = <READ>;
#do your checks here and do whatever
print "$size";
}
I'm not really a human, but I play one on earth.
flash japh
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! —
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.