Update on the usage of sleep()

unstable
sinn3r 2013-06-17 16:05:47 -05:00
parent ed3c5f06eb
commit 9c82c04997
1 changed files with 4 additions and 3 deletions

View File

@ -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. interactive session type specific for the type of exploit.
3. Don't use "sleep". It has been known to cause issues with 3. Don't use "sleep". It has been known to cause issues with
multi-threaded programs on various platforms. Instead, we use multi-threaded programs on various platforms running an older version of
"select(nil, nil, nil, <time>)" throughout the framework. We have Ruby such as 1.8. Instead, we use "select(nil, nil, nil, <time>)" or
found this works around the underlying issue. Rex::sleep() throughout the framework. We have found this works around
the underlying issue.
4. Always use Rex sockets, not ruby sockets. This includes 4. Always use Rex sockets, not ruby sockets. This includes
third-party libraries such as Net::Http. There are several very good third-party libraries such as Net::Http. There are several very good