Warrick Sleeping

[GoogleCodeExporter]

Please describe your feature requests here.

Warrick needlessly sleeping for 2 seconds when the option "no clobber" is 
selected, and a previous session was interrupted, and the -n and -R options are 
not being used.

1) The sleep(2) at line 1030 is commented out
2) The sleep(5) at line 1855 is now a sleep(7)

So, we're not missing any sleep.  It's just that we don't sleep when we already 
have the file and the "no clobber" option has been selected.

Thus, there is less of a need for -n and -R options, since it's less of a pain 
to just kill the process, and re-start it

Also, to possibly step around the problem of being blacklisted by Google or 
anyone else, perhaps calling sleep for random intervals would do the trick, to 
make it seem more like a human being looking at this & that.

Original issue reported on code.google.com by jbrunell...@gmail.com on 5 Sep 2012 at 11:20

[GoogleCodeExporter]

Finished

Original comment by jbrunell...@gmail.com on 28 May 2013 at 5:59

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by jbrunell...@gmail.com on 28 May 2013 at 6:43

• Changed state: Fixed