🚀 go-pugleaf

On Sat 29-Jul-1995  2:22p, Berend Ozceri wrote:

BO> You could redirect the output of the ping command to a file, let it run
BO> for a couple of seconds (like 10 perhaps), and then send a break signal
BO> to it. Then examine the contents of the redirected file to see what the
BO> result was (it could be as simple as searching for "%d bytes received").
BO> All this could be done from an ARexx script, or if you prefer, you could
BO> write a quick C program to do it.

The problem with the PING command is again it requires human intervention. If
AMITCP isn't running, a requestor will appear saying that it must be running
first.  The PING command will HANG forever if you aren't there to hit a button
on the requestor.

The problem is determining if the AmiTCP protocol is up and running.  Not if a
given IP address exists or is reachable.