[pve-devel] [PATCH pve-common 1/2] document run_command

Wolfgang Bumiller w.bumiller at proxmox.com
Tue Sep 15 10:01:32 CEST 2015


---
 src/PVE/Tools.pm | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/src/PVE/Tools.pm b/src/PVE/Tools.pm
index 290b2c3..f25cc4b 100644
--- a/src/PVE/Tools.pm
+++ b/src/PVE/Tools.pm
@@ -242,6 +242,19 @@ sub safe_read_from {
     return $input;
 }
 
+# The $cmd parameter can be:
+#  -) a string
+#    This is generally executed by passing it to the shell with the -c option.
+#    However, it can be executed in one of two ways, depending on whether
+#    there's a pipe involved:
+#      *) with pipe: passed explicitly to bash -c, prefixed with:
+#          set -o pipefail &&
+#      *) without a pipe: passed to perl's open3 which uses 'sh -c'
+#      (Note that this may result in two different syntax requirements!)
+#      FIXME?
+#  -) an array of arguments (strings)
+#    Will be executed without interference from a shell. (Parameters are passed
+#    as is, no escape sequences of strings will be touched.)
 sub run_command {
     my ($cmd, %param) = @_;
 
-- 
2.1.4




More information about the pve-devel mailing list