NAME Sys::Run::Safer - Run external commands, with a safer API VERSION This document describes version 0.01 of Sys::Run::Safer (from Perl distribution Sys-Run-Safer), released on 2014-12-18. SYNOPSIS use Sys::Run::Safer qw(run); run( prog => 'rm', opts => ['-rf', '--interactive=never'], args => ['file1', 'file2', 'dir1'], ) == 0 or die; Will run "system('rm', '-r', '--force', '--interactive=never', '--', 'file1', 'file2', 'dir1')". Upon failure ($? is not zero), will print diagnostic error message. Return value is the same as Perl's "system()". DESCRIPTION Status: experimental, prone to change. This module is an experiment to provide a safer API alternative to Perl's "system()" for executing external commands, particularly commands that follow the POSIX syntax/GNU extension of accepting command-line options/arguments. The problem with Perl's "system()" API is that it *may or may not* execute shell, with relatively complicated rule. Even if you use the list form, e.g. "system 'cmd', @args" it will still use a shell if @args happens to be empty. To always avoid the shell you'll have to use the so-called third form: " system { 'cmd' } 'cmd', @args" which is practically never used by casual programmers, including me. Executing shell sometimes is desired, but brings many consequences like wildcard/pathname expansion, among many other things. You have to be careful to quote every input/argument (e.g. using String::ShellQuote). This module's "run()" currently never invokes shell, by using the third form of "system()". A way to use shell might be provided in the future, but will force the programmer to explicitly express so. There are other CPAN modules that do this (making it clearer when to use shell or not), BTW, e.g. IPC::System::Simple which provides additional "systemx" function which never invokes the shell. Another problem that is seldom addressed by other modules is that programs can mistakenly interpret argument (e.g. filename) as option if that argument happens to start with dash. An example (see [1] for more details) is when there is a file named "--checkpoint-action=exec=sh shell.sh") and you feed it to "tar". Even after you avoid shell or quote the argument, the filename will still be interpreted as an option (and thus the payload shell script executed by "tar") unless you precede the argument in the command with "--". Which is all too easy to be forgotten. Thus, the "run()" API is designed to force you to enter option and argument separately, and automatically add a "--" after the options. FUNCTIONS run(%args) -> bool Run external commands, with a safer API. Arguments ('*' denotes required arguments): * args => *array* * opts => *array* * prog* => *str* Return value: (bool) FAQ What about feeding STDIN, capturing STDOUT/STDERR, timeouts, ...? I plan to incorporate this API, should the API prove to be not too annoying to use, into Proc::Govern. The latter module supports (or will/should support) all kinds of child-controlling features. TODO SEE ALSO [1] Perl's "system()" documentation ("perldoc -f system"). IPC::System::Simple. HOMEPAGE Please visit the project's homepage at . SOURCE Source repository is at . BUGS Please report any bugs or feature requests on the bugtracker website When submitting a bug or request, please include a test-file or a patch to an existing test-file that illustrates the bug or desired feature. AUTHOR perlancar COPYRIGHT AND LICENSE This software is copyright (c) 2014 by perlancar@cpan.org. This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.