summaryrefslogtreecommitdiffstats
path: root/guestfish.pod
diff options
context:
space:
mode:
authorMatthew Booth <mbooth@redhat.com>2009-09-11 17:04:13 +0100
committerMatthew Booth <mbooth@redhat.com>2009-09-14 10:37:50 +0100
commitd5b89d36224b394391af09fba7ed0a7921175610 (patch)
tree1609dbba7ad513ce79980fcd22c0096d8367e1ae /guestfish.pod
parent7eda9e6fb2b1f6504167ab650886f5a336fc6919 (diff)
downloadlibguestfs-d5b89d36224b394391af09fba7ed0a7921175610.tar.gz
libguestfs-d5b89d36224b394391af09fba7ed0a7921175610.tar.xz
libguestfs-d5b89d36224b394391af09fba7ed0a7921175610.zip
guestfish: Redirect stdout when executing remote commands
guestfish --listen necessarily redirects its stdout to /dev/null so as not to interfere with eval. The remote protocol doesn't contain any other provision for collecting stdout for the caller, so executing guestfish --remote will never generate any output. This patch fixes that by forwarding the caller's STDOUT to the listener over the unix socket connection. The listener redirects its STDOUT to the caller's STDOUT for the duration of the command, then closes it again.
Diffstat (limited to 'guestfish.pod')
-rw-r--r--guestfish.pod7
1 files changed, 0 insertions, 7 deletions
diff --git a/guestfish.pod b/guestfish.pod
index 5427b23b..2e50873f 100644
--- a/guestfish.pod
+++ b/guestfish.pod
@@ -394,13 +394,6 @@ You can have several guestfish listener processes running using:
guestfish --remote=$pid1 cmd
guestfish --remote=$pid2 cmd
-=head2 STANDARD OUTPUT DURING REMOTE CONTROL
-
-Because of limitations in the C<eval> statement, stdout from the
-listener is currently redirected to C</dev/null>.
-
-Stderr is unchanged.
-
=head2 REMOTE CONTROL DETAILS
Remote control happens over a Unix domain socket called