Re: fping

[Roland Schemers]

> 
> I like the speed with which it can check a group of hosts.  However, my
> current process records the response time and packet loss for each host;
> I think I would miss that.  Maybe I'll look at this, and see if I can
> add some of those features into it.
> 

I haven't added a feature to ping a host repeatedly yet, but the latest
version will record round trip times and display min/max/avg in the
summary display. For example:

welch-road-gateway is alive (3 msec)
forsythe-gateway is alive (3 msec)
jenkins-gateway is alive (0 msec)
Quad-SW-Gateway is alive (3 msec)
...
SU-SLAC-Gateway is alive (3 msec)
sweet-gateway is alive (0 msec)
CIS-A-Gateway is alive (3 msec)

       29 alive
        0 unreachable
        0 unknown addresses

        0 timeouts (waiting for response)
       29 pings sent
       29 pings received

        0 msec (min round trip time)
        2 msec (avg round trip time)
        7 msec (max round trip time)
    0.429 sec (elapsed real time)

I have also added some other minor changes such as ignoring '#' and blank 
lines when reading from a file. This means you can do stuff like:

fping -ud < /etc/hosts

And print all the hosts that are unreachable. I've also changed some of
the defaults. Someone at DEC actually used fping to ping 20,000 hosts
on DEC's internal network. They had to mess with some of the command line
options, but they got it to work.

I've got the latest version in the pub directory on stanford.edu/barrnet.net
(its the only thing in the pub directory) if you want to take a look.

Roland
--
Roland J. Schemers III              |            Networking Systems
Systems Programmer                  |            168 Pine Hall   (415)-723-6740
Distributed Computing Group         |            Stanford, CA 94305-4122
Stanford University                 |            schemers@Slapshot.Stanford.EDU
- - - - - - - - - - - - - - - - -