+++ This bug was initially created as a clone of Bug #592910 +++
Description of problem:
running 'guestfish --remote run' in a shell command substitution, i.e., `` or $()
would cause the command to hang.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. $ eval `guestfish -a test.img --listen`
2. a=`guestfish --remote run`
we get hang with step 2
the command should return on completion.
--- Additional comment from firstname.lastname@example.org on 2010-05-17 06:59:01 EDT ---
Easy to reproduce.
Something about guestfs_launch interferes with
stdout in a way which is incompatible with the remote
Note this *doesn't* happen with any other command. For example:
$ a=`guestfish --remote list-devices`
$ echo $a
$ a=`guestfish --remote ping-daemon`
$ echo $a
--- Additional comment from email@example.com on 2010-05-17 07:01:11 EDT ---
Created attachment 414520 [details]
strace -o strace.log -f -s 1024 sh -c 'a=`guestfish --remote run`'
--- Additional comment from firstname.lastname@example.org on 2011-08-12 05:41:59 EDT ---
Can this one get at least a documentation fix?
Documented in man page for guestfish:
REMOTE CONTROL RUN COMMAND HANGING
Using the "run" (or "launch") command remotely in a command substitution context hangs, ie. don’t do (note the backquotes):
a=`guestfish --remote run`
Since the "run" command produces no output on stdout, this is not useful anyway.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.