IPC::ConcurrencyLimit - Lock-based limits on cooperative multi-processing River stage one • 6 direct dependents • 6 total dependents

This module implements a mechanism to limit the number of concurrent processes in a cooperative multiprocessing environment. This is an alternative to, for example, running several daemons. Roughly speaking, a typical setup would be the following: * ...

MATTK/IPC-ConcurrencyLimit-0.17 - 02 Nov 2016 16:28:02 GMT

Class::Usul::IPC::Cmd - Execute system commands River stage one • 4 direct dependents • 4 total dependents

Refactored IPC::Cmd with a consistent OO API Would have used MooseX::Daemonize but using Moo not Moose so robbed some code from there instead...

PJFL/Class-Usul-0.84.1 - 14 Apr 2018 12:28:18 GMT

Win32::PowerShell::IPC - Set up IPC between Perl and a PowerShell child process River stage zero No dependents

There's a lot of things in the Microsoft world that can't be done with perl. This is even more true with many Microsoft services offering PowerShell integration instead of more accessible Web APIs. While you can certainly write out a PowerShell scrip...

NERDVANA/Win32-PowerShell-IPC-0.02 - 29 Sep 2017 12:56:04 GMT

IPC::ShellCmd::Generic - Chain a generic wrapper-type command River stage one • 1 direct dependent • 1 total dependent

IPC::ShellCmd::Generic->new(Prog => *$prog*, [*$opt* => *$val*, ...]) The only external method for this is the constructor. This sets up the various arguments that are going to be used to generate the command-line. Other methods on this are used by I...

BOBTFISH/IPC-ShellCmd-0.001 - 09 Nov 2009 01:52:05 GMT

IPC::PerlSSH::Library::IO - a library of file IO functions for IPC::PerlSSH River stage one • 4 direct dependents • 5 total dependents

This module provides a library of functions for interacting with remote IO filehandles. It provides simple wrappers around the perl IO functions, taking or returning file descriptor numbers instead of filehandle objects. This allows filehandles to re...

PEVANS/IPC-PerlSSH-0.17 - 11 Dec 2016 23:23:40 GMT

IPC::PrettyPipe::Executor - role for executor backends River stage one • 1 direct dependent • 1 total dependent

This role defines the required interface for execution backends for IPC::PrettyPipe. Backend classes must consume this role....

DJERIUS/IPC-PrettyPipe-0.12 - 21 Dec 2018 19:41:01 GMT

Class::Usul::Response::IPC - Response class for running external programs River stage one • 4 direct dependents • 4 total dependents

Response class returned by "run_cmd" in Class::Usul::IPC and "popen" in Class::Usul::IPC...

PJFL/Class-Usul-0.84.1 - 14 Apr 2018 12:28:18 GMT

IPC::Open3::Callback::Command - A utility class that provides subroutines for building shell command strings. River stage one • 1 direct dependent • 2 total dependents

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 ...

LTHEISEN/IPC-Open3-Callback-1.19 - 06 Feb 2016 15:30:49 GMT

IPC::Semaphore::SmokeSignals - A mutex and an LRU from crack pipe technology River stage one • 1 direct dependent • 1 total dependent

A friend couldn't get APR::ThreadMutex to work so I offered to roll my own mutual exclusion code when, *bong*, I realized this would be trivial to do with a simple pipe. It is easiest to use as a very simple mutex (see Synopsis above). You can also u...

TYEMQ/IPC-Semaphore-SmokeSignals-0.001002 - 15 Jan 2015 05:10:04 GMT

IPC::PrettyPipe::Stream::Utils - support utilities for streams River stage one • 1 direct dependent • 1 total dependent

Stream Specification A stream specification is a string which may take one of the forms in the *Spec* column: Spec Op Mode File Function ---- --- ---- ---- ----------------------- < < I y read from file via fd 0 <N < I y read from file via fd N > > O...

DJERIUS/IPC-PrettyPipe-0.12 - 21 Dec 2018 19:41:01 GMT

Archive::Tar::Wrapper::IPC::Cmd - Archive::Tar::Wrapper minus IPC::Run, IO::Pty River stage one • 1 direct dependent • 1 total dependent

Archive::Tar::Wrapper::IPC::Cmd is a fork of Michael Schilli's Archive::Tar::Wrapper Removed: IPC::Run, IO::Pty Added: IPC::Cmd...

BIESZCZAD/Archive-Tar-Wrapper-IPC-Cmd-0.22 - 12 Jul 2012 08:43:57 GMT

IPC::ConcurrencyLimit::WithStandby - IPC::ConcurrencyLimit with an additional standby lock River stage one • 6 direct dependents • 6 total dependents

This module provides the same interface as the regular IPC::ConcurrencyLimit module. It differs in what happens if "get_lock" fails to get a slot for the main limit: If it fails to get a (or the) lock on the main limit, it will repeatedly attempt to ...

MATTK/IPC-ConcurrencyLimit-0.17 - 02 Nov 2016 16:28:02 GMT

IPC::Concurrency::DBI::Application - Application identifier that represents the resource that will be limited. River stage zero No dependents

AUBERTG/IPC-Concurrency-DBI-v1.2.0 - 23 Mar 2017 06:00:04 GMT

IPC::Open3::Callback::CommandRunner - A utility class that wraps IPC::Open3::Callback with available output buffers and an option to die on failure instead of returning exit code. River stage one • 1 direct dependent • 2 total dependents

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

LTHEISEN/IPC-Open3-Callback-1.19 - 06 Feb 2016 15:30:49 GMT

IPC::ConcurrencyLimit::WithLatestStandby - IPC::ConcurrencyLimit with latest started working as standby River stage one • 6 direct dependents • 6 total dependents

This module behaves much the same as IPC::ConcurrencyLimit when configured for a single lock, with the exception of what happens when the lock is already held by another process. Instead of simply returning false, the lock will block and the worker w...

MATTK/IPC-ConcurrencyLimit-0.17 - 02 Nov 2016 16:28:02 GMT

IPC::Open3::Callback::CommandFailedException - An exception thrown when run_or_die encounters a failed command River stage one • 1 direct dependent • 2 total dependents

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...

LTHEISEN/IPC-Open3-Callback-1.19 - 06 Feb 2016 15:30:49 GMT

76 results (0.045 seconds)