#
#
# patch "monotone.texi"
#  from [b3070e2f7b2552c00e0c3dbad657529af500cdb1]
#    to [ae7f2f8151bb0ca219a0d2d94bc1dcadccb0538c]
#
============================================================
--- monotone.texi	b3070e2f7b2552c00e0c3dbad657529af500cdb1
+++ monotone.texi	ae7f2f8151bb0ca219a0d2d94bc1dcadccb0538c
@@ -7748,7 +7748,9 @@ @section Automation
 standard error and exits with nonzero status. Errors in the commands run
 through this interface do not affect the exit status. Instead, the <err code>
 field in the output is set to 2, and the output of the command becomes
-whatever error message would have been given.
+whatever error message would have been given. Trying to run the
address@hidden stdio} or @code{automate remote_stdio} commands will always
+act as if that command encountered an error.
 
 @end table
 
@@ -7778,6 +7780,14 @@ @section Automation
 
 There will be some extra chatter on stderr unless @option{--quiet} is given.
 
address@hidden Error Conditions
+
+If left idle for too long or there are network problems, the connection to the
+server may be dropped. This will not be detected while monotone is waiting for
+input. Instead, when a complete command has been entered and monotone tries to
+send it to the remote server it will print a message to stderr and exit with
+code 1.
+
 @end table
 
 @item mtn automate genkey @var{name} @var{passphrase}