by jimbobo2779 » Mon Feb 13, 2012 11:35 am
@farrow:
The proxy harvesting works exactly as you described it "not working" it searches for proxies, checks them and removes the non working ones. Most public proxies are bad, this is exactly why a harvester is needed.
The delay is for how long to post before switching back to the harvesting proxies mode. Only so many proxies will be checked before switching back to posting mode, I have outlined how the process works to show that it cannot run endlessly:
1) 5 pages worth of proxies are pulled from random pages (random from a pre-defined list)
2) Each proxy from the 5 pages is added to a list and checked for duplicates
3) Each proxy is then checked one by one with non-working or transparent proxies being disregarded
4) Working proxies are added to a list of working harvested proxies
5) If Working proxies is above the harvest limit set in the settings stop the process and disregard further unchecked proxies
6) If list exhausted switch back to posting mode
There is no loop to prevent switching back to posting mode and the proxy harvesting mode ends once all proxies are checked which unless you are running less than 10 threads is unlikely to run for more than 15minutes with it finishing in 5 or less in the majority of cases.
Also as I replied to fastcooler in his thread the log is truncated when it reachesa certain size, as proxy checking is much quicker (more jobs done in the same amount of time) than posting the log reaches the truncation size very quickly and therefore you cannot reliably see how long a process such as proxy harvesting has actually been running for.