diff --git a/tsshbatch.rst b/tsshbatch.rst
index e0876de..a1fe267 100644
--- a/tsshbatch.rst
+++ b/tsshbatch.rst
@@ -6,7 +6,7 @@
 SYNOPSIS
 --------
 
-tsshbatch.py [-hvk] [-n name] [-p pw] [-H 'h1 h2 ...' | hostlistfile] command arg ...
+tsshbatch.py [-ehvk] [-n name] [-p pw] [-H 'h1 h2 ...' | hostlistfile] command arg ...
 
 
 DESCRIPTION
@@ -29,12 +29,13 @@
 OPTIONS
 -------
 
+  -H 'hostlist'   Single quoted list of hosts on which to run the command
+  -e              Don't report remote host stderr output
   -h              Print help information
-  -v              Print detailed program version information and exit
   -k              Use ssh keys instead of name/password credentials
   -n name         Login name to use
   -p pw           Password to use when logging in and/or doing sudo
-  -H hostlist     Single quoted list of hosts on which to run the command
+  -v              Print detailed program version information and exit
 
 
 ENVIRONMENT
@@ -244,8 +245,27 @@
 BUGS AND MISFEATURES
 --------------------
 
-None known as of this release.
+When ``sudo`` is presented a bad password, it ordinarily prints a
+string indicating something is wrong.  ``tsshbatch`` looks for this to
+let you know that you've got a problem and then terminates further
+operation.  This is so that you do not attempt to log in with a bad
+password across all the servers you have targeted.  (Many enterprises
+have policies to lock out a user ID after some small number of failed
+login/access attempts.)
 
+However, some older versions of ``sudo`` (noted on a RHEL 4 server
+running ``sudo`` 1.6.7p5) do not return any feedback when presented
+with a bad password.  This means that ``tsshbatch`` cannot tell the
+difference between a successful ``sudo`` and a system waiting for you
+to reenter a proper password.  In this situation, if you enter a bad
+password, the *the program will hang*.  Why?  ``tsshbatch`` thinks
+nothing is wrong and waits for the ``sudo`` command to complete.  At
+the same time, ``sudo`` itself is waiting for an updated password.  In
+this case, you have to kill ``tsshbatch`` and start over.  This
+typically requires you to put the program in background (```Ctrl-Z``
+in most shells) and then killing that job from the command line.
+
+There is no known workaround for this problem.
 
 COPYRIGHT AND LICENSING
 -----------------------
@@ -272,7 +292,7 @@
 
 ::
 
-  $Id: tsshbatch.rst,v 1.105 2011/12/30 20:31:34 tundra Exp $
+  $Id: tsshbatch.rst,v 1.106 2012/01/05 18:48:32 tundra Exp $
 
 You can find the latest version of this program at: