X-Git-Url: http://git.annexia.org/?a=blobdiff_plain;f=virt-what.pod;h=4304297d4f813746b3634ae5a3eb877d19150dc9;hb=f9bf43287a6278ad43f3d5a3931e57f8826692af;hp=156406ecc12c952a0be9c3daaa079cbebde499ce;hpb=5453cf333745418a641374e19fd968519fd7de30;p=virt-what.git

diff --git a/virt-what.pod b/virt-what.pod
index 156406e..4304297 100644
--- a/virt-what.pod
+++ b/virt-what.pod
@@ -95,7 +95,8 @@ Status: contributed by Justin Clift
 
 The guest is running inside IBM PowerVM Lx86 Linux/x86 emulator.
 
-Status: data supplied by Jeffrey Scheel, not confirmed
+Status: data originally supplied by Jeffrey Scheel, confimed by
+Yufang Zhang and RWMJ
 
 =item B<qemu>
 
@@ -179,6 +180,24 @@ whether C<virt-what> managed detection "correctly" (which is basically
 unknowable given the large variety of virtualization systems out there
 and that some systems deliberately emulate others).
 
+=head1 RUNNING VIRT-WHAT FROM OTHER PROGRAMS
+
+C<virt-what> is designed so that you can easily run it from
+other programs or wrap it up in a library.
+
+Your program should check the exit status (see the section above).
+
+Some programming languages (notably Python: issue 1652) erroneously
+mask the C<SIGPIPE> signal and do not restore it when executing
+subprocesses.  C<virt-what> is a shell script and some shell commands
+do not work correctly when you do this.  You may see warnings from
+C<virt-what> similar to this:
+
+ echo: write error: Broken pipe
+
+The solution is to set the C<SIGPIPE> signal handler back to C<SIG_DFL>
+before running C<virt-what>.
+
 =head1 IMPORTANT NOTE
 
 Most of the time, using this program is the I<wrong> thing to do.