Author: Antoine Amarilli <email@example.com>
Date: Wed, 26 Jun 2013 15:08:52 +0200
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/README b/README
@@ -373,7 +373,7 @@ addressed to each individual channel.
Beware of the fact that the IRC server may limit irctk's rate in a fashion which
irctk will not be able to control, so any slowdowns you see may not be irctk's
-fault. Use -o to know when irctk is sending messages, to see who is slowing
+fault. Use -o to see when irctk is sending your messages, to see who is slowing
== 4. Test suite ==
@@ -395,8 +395,8 @@ ircd-hybrid, look at "can_flood" and also at "default_floodcount").
irctk will exit whenever it has sent all messages on stdin to the server. If the
server throttles it, then it might exit before all messages have been
-delivered, and some may get lost. Use -i, or sleep for a few seconds before
+delivered, and some may get lost. Use -i and -I, or sleep for a few seconds
+before closing stdin.
You need to use tail -f /dev/null as input to background irctk without having it
suspend or exit (see above).