package Unix::Process;
use strict;
use warnings;
use Carp;
use IPC::System::Simple qw(capturex);
our $VERSION = '1.3101';
our $PS_PROGRAM = $ENV{PS_PATH} || '/bin/ps';
our $AUTOLOAD;
1;
sub AUTOLOAD {
die "unprocessable garbage: $AUTOLOAD" unless $AUTOLOAD =~ m/::(\w+)$/;
my $sub = $1;
my $f = sub {
my $this = shift;
my $pid = shift; $pid = $$ unless $pid and int($pid);
my $result = eval { capturex($PS_PROGRAM, '-o', $sub, '-p', $pid) };
croak $@ if $@;
return $1 if $result =~ m/[\r\n]\s*(.+?)\s*[\r\n]/ms;
return;
};
{
no strict 'refs';
*{$AUTOLOAD} = $f;
}
goto &$f;
}
__END__
# Below is stub documentation for your module. You better edit it!
=head1 NAME
Unix::Process - Perl extension to get pid info from (/bin/ps).
=head1 SYNOPSIS
use Unix::Process;
my $vsz = Unix::Process->vsz($$);
my $pid = Unix::Process->pid;
=head1 DESCRIPTION
All fields from the ps command can be fetched by calling a function of their
name (see SYNOPSIS). If the pid is not given as an argument to the function,
$$ (cur pid) is assumed.
This module is really just a giant AUTOLOAD to interact with the /bin/ps
command. I suppose I could be talked into doing something real with it some
day.
You can manually set the C<$Unix::Process::PS_PROGRAM = "/opt/bin/ps"> by hand,
or you can set C<$ENV{PS_PATH} = "/usr/local/bin/ps">, but you must somehow
instruct Unix::Process on the location of ps. Otherwise, it will guess
C<"/bin/ps">.
=head1 AUTHOR
Paul Miller C<< <jettero@cpan.org> >>
I am using this software in my own projects... If you find bugs, please
please please let me know. :) Actually, let me know if you find it handy at
all. Half the fun of releasing this stuff is knowing that people use it.
=head1 COPYRIGHT
Copyright (c) 2007-2009 Paul Miller -- LGPL
=head1 SEE ALSO
perl(1), ps
=cut
