|
|
| |
Proc::Background(3) |
User Contributed Perl Documentation |
Proc::Background(3) |
Proc::Background - Generic interface to Unix and Win32 background process
management
use Proc::Background;
timeout_system($seconds, $command, $arg1, $arg2);
timeout_system($seconds, "$command $arg1 $arg2");
my $proc1 = Proc::Background->new($command, $arg1, $arg2) || die "failed";
my $proc2 = Proc::Background->new("$command $arg1 1>&2") || die "failed";
if ($proc1->alive) {
$proc1->terminate;
$proc1->wait;
}
say 'Ran for ' . ($proc1->end_time - $proc1->start_time) . ' seconds';
Proc::Background->new({
autodie => 1, # Throw exceptions instead of returning undef
cwd => 'some/path/', # Set working directory for the new process
exe => 'busybox', # Specify executable different from argv[0]
command => [ $command ] # resolve ambiguity of command line vs. argv[0]
});
# Set initial file handles
Proc::Background->new({
stdin => undef, # /dev/null or NUL
stdout => '/append/to/fname', # will try to open()
stderr => $log_fh, # use existing handle
command => \@command,
});
# Automatically kill the process if the object gets destroyed
my $proc4 = Proc::Background->new({ autoterminate => 1 }, $command);
$proc4 = undef; # calls ->terminate
This is a generic interface for placing processes in the background on both Unix
and Win32 platforms. This module lets you start, kill, wait on, retrieve exit
values, and see if background processes still exist.
- new [options] command, [arg, [arg, ...]]
- new [options] 'command [arg [arg ...]]'
- This creates a new background process. Just like
"system()", you can supply a single
string of the entire command line, or individual arguments. The first
argument may be a hashref of named options. To resolve the ambiguity
between a command line vs. a single-element argument list, see the
"command" option below.
By default, the constructor returns an empty list on failure,
except for a few cases of invalid arguments which call
"croak".
For platform-specific details, see "IMPLEMENTATION"
in Proc::Background::Unix or "IMPLEMENTATION" in
Proc::Background::Win32, but in short:
- Unix
- This implementation uses
"fork"/"exec".
If you supply a single-string command line, it is passed to the shell. If
you supply multiple arguments, they are passed to
"exec". In the multi-argument case, it
will also check that the executable exists before calling
"fork".
- Win32
- This implementation uses the Windows CreateProcess API. If you supply a
single-string command line, it derives the executable by parsing the
command line and looking for the first element in the
"PATH", appending
".exe" if needed. If you supply multiple
arguments, the first is used as the
"exe" and the command line is built
using Win32::ShellQuote.
Options:
- "autodie"
- This module traditionally has returned
"undef" if the child could not be
started. Modern Perl recommends the use of exceptions for things like
this. This option, like Perl's autodie pragma, causes all fatal errors in
starting the process to die with exceptions instead of returning
undef.
- "command"
- You may specify the command as an option instead of passing the command as
a list. A string value is considered a command line, and an arrayref value
is considered an argument list. This can resolve the ambiguity between a
command line vs. single-element argument list.
- "exe"
- Specify the executable. This can serve two purposes: on Win32 it avoids
the parsing of the commandline, and on Unix it can be used to run an
executable while passing a different value for
$ARGV[0].
- "stdin", "stdout", "stderr"
- Specify one or more overrides for the standard handles of the child. The
value should be a Perl filehandle with an underlying system
"fileno" value. As a convenience, you
can pass "undef" to open the
"NUL" device on Win32 or
"/dev/null" on Unix. You may also pass a
plain-scalar file name which this module will attmept to open for reading
or appending.
(for anything more elaborate, see IPC::Run instead)
Note that on Win32, none of the parent's handles are inherited
by default, which is the opposite on Unix. When you specify any of these
handles on Win32 the default will change to inherit them from the
parent.
- "cwd"
- Specify a path which should become the child process's current working
directory. The path must already exist.
- "autoterminate"
- If you pass a true value for this option, then destruction of the
Proc::Background object (going out of scope, or script-end) will kill the
process via "->terminate". Without
this option, the child process continues running.
"die_upon_destroy" is an alias for this
option, used by previous versions of this module.
- command
- The command (string or arrayref) that was passed to the constructor.
- exe
- The path to the executable that was passed as an option to the
constructor, or derived from the
"command".
- start_time
- Return the value that the Perl function time() returned when the
process was started.
- pid
- Returns the process ID of the created process. This value is saved even if
the process has already finished.
- alive
- Return 1 if the process is still active, 0 otherwise. This makes a
non-blocking call to "wait" to check the
real status of the process if it has not been reaped yet.
- suspended
- Boolean whether the process is thought to be stopped. This does not
actually consult the operating system, and just returns the last known
status from a call to "suspend" or
"resume". It is always false if
"alive" is false.
- exit_code
- Returns the exit code of the process, assuming it exited cleanly. Returns
"undef" if the process has not exited
yet, and 0 if the process exited with a signal (or TerminateProcess).
Since 0 is ambiguous, check for
"exit_signal" first.
- exit_signal
- Returns the value of the signal the process exited with, assuming it died
on a signal. Returns "undef" if it has
not exited yet, and 0 if it did not die to a signal.
- end_time
- Return the value that the Perl function time() returned when the
exit status was obtained from the process.
- autoterminate
- This writeable attribute lets you enable or disable the autoterminate
option, which could also be passed to the constructor.
- wait
-
$exit= $proc->wait; # blocks forever
$exit= $proc->wait($timeout_seconds); # since version 1.20
Wait for the process to exit. Return the exit status of the
command as returned by wait() on the system. To get the actual
exit value, divide by 256 or right bit shift by 8, regardless of the
operating system being used. If the process never existed, this returns
undef. This function may be called multiple times even after the process
has exited and it will return the same exit status.
Since version 1.20, you may pass an optional argument of the
number of seconds to wait for the process to exit. This may be
fractional, and if it is zero then the wait will be non-blocking. Note
that on Unix this is implemented with "alarm" in Time::HiRes
before a call to wait(), so it may not be compatible with scripts
that use alarm() for other purposes, or systems/perls that resume
system calls after a signal. In the event of a timeout, the return will
be undef.
- suspend
- Pause the process. This returns true if the process is stopped afterward.
This throws an excetion if the process is not
"alive" and
"autodie" is enabled.
- resume
- Resume a paused process. This returns true if the process is not stopped
afterward. This throws an exception if the process is not
"alive" and
"autodie" is enabled.
- terminate, terminate(@kill_sequence)
- Reliably try to kill the process. Returns 1 if the process no longer
exists once terminate has completed, 0 otherwise. This will also
return 1 if the process has already exited.
@kill_sequence is a list of actions
and seconds-to-wait for that action to end the process. The default is
" TERM 2 TERM 8 KILL 3 KILL 7 ". On
Unix this sends SIGTERM and SIGKILL; on Windows it just calls
TerminateProcess (graceful termination is still a TODO).
Note that "terminate()"
(formerly named "die()") on
Proc::Background 1.10 and earlier on Unix called a sequence of:
->die( ( HUP => 1 )x5, ( QUIT => 1 )x5, ( INT => 1 )x5, ( KILL => 1 )x5 );
which wasn't what most people need, since SIGHUP is open to
interpretation, and QUIT is almost always immediately fatal and
generates a coredump. The new default should accomodate programs that
acknowledge a second SIGTERM, and give enough time for it to exit on a
laggy system while still not holding up the main script too much.
"die" is preserved as an
alias for "terminate".
This throws an exception if the process has been reaped and
"autodie" is enabled.
- timeout_system timeout, command, [arg,
[arg...]]
- timeout_system 'timeout command [arg
[arg...]]'
- Run a command for timeout seconds and if the process did not exit,
then kill it.
In a scalar context, timeout_system returns the exit
status from the process. In an array context, timeout_system
returns a two element array, where the first element is the exist status
from the process and the second is set to 1 if the process was killed by
timeout_system or 0 if the process exited by itself.
The exit status is the value returned from the wait()
call. If the process was killed, then the return value will include the
killing of it. To get the actual exit value, divide by 256.
If something failed in the creation of the process, the
subroutine returns an empty list in a list context, an undefined value
in a scalar context, or nothing in a void context.
- IPC::Run
- IPC::Run is a much more complete solution for running child processes. It
handles dozens of forms of redirection and pipe pumping, and should
probably be your first stop for any complex needs.
However, also note the very large and slightly alarming list
of limitations it lists for Win32. Proc::Background is a much simpler
design and should be more reliable for simple needs.
- Win32::ShellQuote
- If you are running on Win32, this article by Daniel Colascione helps
describe the problem you are up against for passing argument lists:
Everyone quotes command line arguments the wrong way
<https://blogs.msdn.microsoft.com/twistylittlepassagesallalike/2011/04/23/everyone-quotes-command-line-arguments-the-wrong-way/>
This module gives you parsing / quoting per the standard
CommandLineToArgvW behavior. But, if you need to pass arguments to be
processed by "cmd.exe" then you need
to do additional work.
- Blair Zajac <blair@orcaware.com>
- Michael Conrad <mike@nrdvana.net>
- Florian Schlichting <fsfs@debian.org>
- Kevin Ryde <user42@zip.com.au>
- Salvador Fandiño <sfandino@yahoo.com>
This software is copyright (c) 2021 by Michael Conrad, (C) 1998-2009 by Blair
Zajac.
This is free software; you can redistribute it and/or modify it
under the same terms as the Perl 5 programming language system itself.
Visit the GSP FreeBSD Man Page Interface. Output converted with ManDoc. |