Hello Toke, I have tested the latest commit related to timeout (-t option for fping v4.0). It is working fine.
I am curious to know is there any specific reason for keeping the timeout so large (two times of total execution)? Are you sure that it will not affect the tool functionality in case the host is unreachable? Regards, Sourabh Jain On Mon, Apr 9, 2018 at 9:06 PM, Sourabh jain <jainsourabh...@gmail.com> wrote: > Yeah, sure. I will do it. > > On Mon, Apr 9, 2018 at 6:13 PM, Toke Høiland-Jørgensen <t...@toke.dk> > wrote: > >> Toke Høiland-Jørgensen <t...@toke.dk> writes: >> >> > Sourabh jain <jainsourabh...@gmail.com> writes: >> > >> >> Yes I have tested this behaviour with latest fping (v4.0). Till fping >> v3.16 >> >> it was working fine even if delay is higher than the per host interval. >> >> >> >> You can verify this behaviour with the screenshot that I have attached. >> >> >> >> In the image three sample has been taken with different interval. You >> can >> >> easily identify for a particular sequence if ICMP reply comes after the >> >> sending interval fping won't consider it. >> >> >> >> Here is the discussion related to timeout and -p option. >> >> https://github.com/schweikert/fping/issues/32 >> > >> > Ah, so yeah, this is a new issue with fping 4.0. Great. >> > >> > I'll look into adding a workaround... :) >> >> Pushed a workaround to Flent git. Could you test that, please? >> >> -Toke >> > >
_______________________________________________ Flent-users mailing list Flent-users@flent.org http://flent.org/mailman/listinfo/flent-users_flent.org
