This bug has something to do with the blocking ping, because the ping method
returns only after a reply or timeout, thus increasing the interval to the
next schedule ping to the same host and to the other hosts.
+
+- If one ping fails, the subsequent analysis report that the ping is down:
+ Example:
+ Request timed out
+ - Host down: www.ufsc.br
+ - Speeding up ping interval to: 30s <-- should speed up, OK
+ - Time elapsed since last ping: 65s <-- elapsed time, OK
+ 20 bytes from 150.162.2.10: icmp_seq=1 ttl=47 time=252 ms
+ - Host down: www.ufsc.br <-- dammit! It is not down, WRONG
+ - Speeding up ping interval to: 30s <-- should not speed up again, WRONG
+ - Time elapsed since last ping: 31s <-- elapsed time, OK, but should go
+ back to original
+ 20 bytes from 150.162.2.10: icmp_seq=1 ttl=47 time=253 ms
+ - Host down: www.ufsc.br
+ - Speeding up ping interval to: 30s
+ - Time elapsed since last ping: 31s