X-Git-Url: http://git.annexia.org/?a=blobdiff_plain;f=virt-what.pod;h=99547c0dba70628739322cc0b26841c139b655df;hb=b12933e28ac504f461dc1a2f9d4682c72f538d0e;hp=156406ecc12c952a0be9c3daaa079cbebde499ce;hpb=039a077e5531bc53703caf6474ed23573eae4d2b;p=virt-what.git

diff --git a/virt-what.pod b/virt-what.pod
index 156406e..99547c0 100644
--- a/virt-what.pod
+++ b/virt-what.pod
@@ -179,6 +179,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.