tidying

[users/heiko/exim.git] / test / README

diff --git a/test/README b/test/README
index 903c8abee69f60454d5e4d2677d24e19b25305e2..e544857889535c0c54a6f5e6bd793742263d4e9e 100644 (file)
--- a/test/README
+++ b/test/README
@@ -677,7 +677,7 @@ only when DBM support is available in Exim, and typically follows the use of a
 "write" command (see below) that creates the input file.
 
 
-  dumpdb <dbname>
+  dump <dbname>
 
 This command runs the exim_dumpdb utility on the testing spool directory, using
 the database name given, for example: "dumpdb retry".
@@ -731,7 +731,7 @@ to the screen.
   munge <name>
 
 This command requests custom munging of the test outputs.  The munge names
-used are coded in the runtest script.
+used are coded in the runtest script (look for 'name of munge').
 
 
   need_ipv4
@@ -836,7 +836,7 @@ This command runs the auxiliary "client" program that simulates an SMTP client.
 It is controlled by a script read from its standard input, details of which are
 given below. There are two options. One is -t, which must be followed directly
 by a number, to specify the command timeout in seconds (e.g. -t5). The default
-timeout is 1 second. The other option is -tls-on-connect, which causes the
+timeout is 5 seconds. The other option is -tls-on-connect, which causes the
 client to try to start up a TLS session as soon as it has connected, without
 using the STARTTLS command. The client program connects to the given IP address
 and port, using the specified interface, if one is given.
@@ -897,13 +897,15 @@ input, details of which are given below. A number of options are implemented:
 
   -d       causes the server to output debugging information
 
-  -t       sets a timeout in seconds (default 5) for when the server is
+  -t <sec> sets a timeout (default 5) for when the server is
            awaiting an incoming connection
 
   -noipv4  causes the server not to set up an IPv4 socket
 
   -noipv6  causes the server not to set up an IPv6 socket
 
+  -i <sec> sets an initial pause, to delay before creating the listen sockets
+
 By default, in an IPv6 environment, both kinds of socket are set up. However,
 the test script knows which interfaces actually exist on the host, and it adds
 -noipv4 or -noipv6 to the server command as required. An error occurs if both