sashac88 has asked for the wisdom of the Perl Monks concerning the following question:

Dear monks,
I'm trying to come up with something that will print the memory
load on a machine every time I run it. It'll be best if I won't have
to deal with parsing the output from various OS tools. I need it
for several different Operating systems. Is there a module already
written for this? Every suggestion is appreciated.
Many thanks.

Replies are listed 'Best First'.
Re: monitoring memory load
by zentara (Cardinal) on Mar 15, 2009 at 15:18 UTC
    "top" or a "top-like utility" should be availalble on most Linux type systems. There is also Proc::ProcessTable. ( I usually do Tk/Gtk2 guis for these things, but you may want commandline for a server-load monitor. ) For windows, maybe see: monitoring CPU usage
    #!/usr/bin/perl -w # Description: Fool a process into # thinking that STDOUT is a terminal, when in fact # it may be a file or a pipe. This can be useful # with programs like ps and w on linux... which # will trunc their output to the width of the # terminal, and, if they cannot detect the terminal # width, use a default 80 columns. Wouldn't it be # nice to say "ps -aux | grep etcshadow", and get # output that looks like when you just say "ps # -aux"? Well, that's the idea. #try ./pseudotty "xterm -e top" #or ./pseudotty top use warnings; use strict; use IO::Pty; die "usage: ptyexec command [args]\n" unless @ARGV; my $pty = IO::Pty->new; my $slave = $pty->slave; open TTY,"/dev/tty" or die "not connected to a terminal\n"; $pty->clone_winsize_from(\*TTY); close TTY; my $pid = fork(); die "bad fork: $!\n" unless defined $pid; if (!$pid) { # $slave->close(); open STDOUT,">&=".$pty->fileno() or die $!; exec @ARGV; }else{ $pty->close(); while (defined (my $line = <$slave>)) { print $line; } } #cleanup pty for next run $pty->close();

    I'm not really a human, but I play one on earth My Petition to the Great Cosmic Conciousness
      On the linux side, the "vmstat" program may be a better choice than "top" (and its peers). "vmstat" only reports memory information and should not place a computational burden on the CPU the way "top" can. You can also access this information directly by reading the pseudo-file "/proc/vmstat".