Re: fping.monitor output problems

2006-12-20 Thread Ed Ravin
On Tue, Dec 13, 2005 at 04:53:21PM +0100, Hans Kinwel wrote: > > I finally went to the bottom of this. Not that it is rocket science. > > When I do fping 1.2.3.4 I get > > ICMP Host Unreachable from 194.178.10.133 for ICMP Echo sent to 1.2.3.4 > ICMP Host Unreachable from 194.178.10.133 for ICM

Re: fping.monitor output problems

2005-12-13 Thread Hans Kinwel
On 09/01/2005 03:50 AM, Ed Ravin wrote: On Thu, Jul 07, 2005 at 01:05:13PM +0200, Kevin Ivory wrote: On 2005-07-07 13:00, Kevin Ivory wrote: the fping.monitor included with mon-1.0.0pre5 doesn't semm to parse the output of fping correctly. ... # ./fping.monitor 192.168.140.3 192.168.140.3

Re: fping.monitor output problems

2005-08-31 Thread Ed Ravin
On Thu, Jul 07, 2005 at 01:05:13PM +0200, Kevin Ivory wrote: > On 2005-07-07 13:00, Kevin Ivory wrote: > >the fping.monitor included with mon-1.0.0pre5 doesn't semm to parse > >the output of fping correctly. > ... > ># ./fping.monitor 192.168.140.3 > >192.168.140.3 ICMP ICMP ICMP ICMP > > some mor

Re: fping.monitor output problems

2005-07-07 Thread Kevin Ivory
On 2005-07-07 13:00, Kevin Ivory wrote: the fping.monitor included with mon-1.0.0pre5 doesn't semm to parse the output of fping correctly. ... # ./fping.monitor 192.168.140.3 192.168.140.3 ICMP ICMP ICMP ICMP some more extra information: the problematic code must have went in between pre3 and

fping.monitor output problems

2005-07-07 Thread Kevin Ivory
the fping.monitor included with mon-1.0.0pre5 doesn't semm to parse the output of fping correctly. (Extra info: Depending of the fping, the combination of default options used in fping.monitor works in 1.5s for the old version an 16s for the recent version.) This happens both with SUSE with fpin