Extremely similar to open2(), open3() spawns the given $cmd and connects CHLD_OUT for reading from the child, CHLD_IN for writing to the child, and CHLD_ERR for errors. If CHLD_ERR is false, or the same file descriptor as CHLD_OUT, then STDOUT and ST...

Extremely similar to open2(), open3() spawns the given $cmd and connects CHLD_OUT for reading from the child, CHLD_IN for writing to the child, and CHLD_ERR for errors. If CHLD_ERR is false, or the same file descriptor as CHLD_OUT, then STDOUT and ST...

The goals of this module are: 1 Encapsulate logic done every time you want to use open3(). 2 boolean check of command execution 3 Out of the box printing to STDOUT/STDERR or assignments to variables (see #5) 4 open3() error reporting 5 comprehensive ...

IPC::Open3::Simple aims at making it very easy to start a shell command, eventually feed its stdin with some data, then retrieve its stdout and stderr separately. When you want to run a shell command and parse its stdout/stderr or feed its stdin, you...

This module feeds output and error stream from a command to supplied callbacks. Thus, this class removes the necessity of dealing with IO::Select by hand and also provides a workaround for the bad reputation associated with Microsoft Windows' IPC....

This provides a very basic logger for when Log4perl is not available....

Adds more convenience to IPC::Open3::Callback by buffering output and error if needed and dieing on failure if wanted....

The subroutines exported by this module can build shell command strings that can be executed by IPC::Open3::Callback, IPC::Open3::Callback::CommandRunner, ``, system(), or even plain old open 1, 2, or 3. There is not much point to *shelling* out for ...

This provides a container for information obtained when a command fails. The "command" and "exit_status" will always be available, but "out" and "err" will only be present if you supply the command option "out_buffer => 1" and "err_buffer => 1" respe...

IPC::RunExternal is for executing external operating system programs more conveniently than with `` or "system()", and without all the hassle of IPC::Open3. IPC::RunExternal allows: 1) Capture stdout and stderr in scalar variables. 2) Capture both st...

IPC::Cmd allows you to run commands platform independently, interactively if desired, but have them still work. The "can_run" function can tell you if a certain binary is installed and if so where, whereas the "run" function can actually execute any ...

This module was written to provide a secure and highly flexible way to execute external programs with an intuitive syntax. In addition, more info is returned with each string of executions, such as the list of PIDs and $? of the last external pipe pr...

IPC::Run allows you to run and interact with child processes using files, pipes, and pseudo-ttys. Both system()-style and scripted usages are supported and may be mixed. Likewise, functional and OO API styles are both supported and may be mixed. Vari...

This module allows you to run a subprocess and redirect stdin, stdout, and/or stderr to files and perl data structures. It aims to satisfy 99% of the need for using "system", "qx", and "open3" with a simple, extremely Perlish API. Speed, simplicity, ...

The open2() function runs the given $cmd and connects $chld_out for reading and $chld_in for writing. It's what you think should work when you try $pid = open(HANDLE, "|cmd args|"); The write filehandle will have autoflush turned on. If $chld_out is ...

The open2() function runs the given $cmd and connects $chld_out for reading and $chld_in for writing. It's what you think should work when you try $pid = open(HANDLE, "|cmd args|"); The write filehandle will have autoflush turned on. If $chld_out is ...

THIS SOFTWARE IS STILL UNDER DEVELOPMENT PLEASE REPORT ANY BUGS, COMMENTS, OR FEATURE REQUESTS In the spirit of IPC::Open2 and IPC::Open3, which give you 2 and 3 handles to a child process, IPC::OpenAny makes it easy to start a process with any file ...

This module encapsulates the open3() function call (see IPC::Open3) and its associated filehandles. This makes it easy to maintain multiple interactive command sessions, such as multiple persistent 'ssh' and/or 'rsh' sessions, within the same perl sc...

IPC::Capture is a module for running external applications in a portable fashion when you're primarily interested in capturing the returned output. Essentially this is an attempt at creating a portable way of doing "backticks" with io-redirection. In...

IPC::Pipeline exports a single function "pipeline()". Similar in calling convention to IPC::Open3, "pipeline()" spawns N children, connecting the first child to the $first_child_in handle, the final child to $last_child_out, and each child to a share...