From 9c82c0499733700f9f3a2c7ee6fbd0d5288cbbc7 Mon Sep 17 00:00:00 2001
From: sinn3r <wei_chen@rapid7.com>
Date: Mon, 17 Jun 2013 16:05:47 -0500
Subject: [PATCH] Update on the usage of sleep()

---
 HACKING | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/HACKING b/HACKING
index 04b284e08e..abf5776c67 100644
--- a/HACKING
+++ b/HACKING
@@ -37,9 +37,10 @@ need user input, you can either register an option or expose an
 interactive session type specific for the type of exploit.
 
 3. Don't use "sleep". It has been known to cause issues with
-multi-threaded programs on various platforms. Instead, we use
-"select(nil, nil, nil, <time>)" throughout the framework. We have
-found this works around the underlying issue.
+multi-threaded programs on various platforms running an older version of
+Ruby such as 1.8. Instead, we use "select(nil, nil, nil, <time>)" or
+Rex::sleep() throughout the framework. We have found this works around
+the underlying issue.
 
 4. Always use Rex sockets, not ruby sockets.  This includes
 third-party libraries such as Net::Http.  There are several very good