process ids

[Robert Mohr]

Is there a way for a program outside of Perl to be run in the background
and have Perl store the process id. That is, if I want to run the
program 'program', I could run something similar to `program &` and get
something like '[1] 12834' from it (what I'd get from running 'program
&' from the command line).

 

[Ben Morrow]

Is there a way for a program outside of Perl to be run in the background
and have Perl store the process id. That is, if I want to run the
program 'program', I could run something similar to `program &` and get
something like '[1] 12834' from it (what I'd get from running 'program
&' from the command line).

(untested)

use POSIX qw/:sys_wait_h/;

$SIG{CHLD} = sub { 1 while 0 < waitpid -1, WNOHANG };

my $pid = fork;
defined $pid or die "can't fork: $!";
$pid or exec "program";

Ben

 

[Robert Mohr]

Is there a way for a program outside of Perl to be run in the background
and have Perl store the process id. That is, if I want to run the
program 'program', I could run something similar to `program &` and get
something like '[1] 12834' from it (what I'd get from running 'program
&' from the command line).

(untested)

use POSIX qw/:sys_wait_h/;

$SIG{CHLD} = sub { 1 while 0 < waitpid -1, WNOHANG };

my $pid = fork;
defined $pid or die "can't fork: $!";
$pid or exec "program";

Thank you. One more question though: how do you kill the process from
the id? Can it be done through Perl (I assume it can, but can't find
out how from perldoc POSIX, which is rather confusing) or must I do it
through sh?

 

[Paul Lalli]

Thank you. One more question though: how do you kill the process from
the id? Can it be done through Perl (I assume it can, but can't find
out how from perldoc POSIX, which is rather confusing) or must I do it
through sh?

perldoc -f kill


Paul Lalli

 

[Robert Mohr]

perldoc -f kill

Guess that makes sense. Thank you.