🚀 go-pugleaf

David Evans (devans@ccubb.com) wrote:

: 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.

Not necessarily. It depends on how you have AmiTCP configured. I can start
AmiTCP on my machine without connecting to a remote host. A check to see
if it was up and running would be positive, but I wouldn't be connected
to any other host.

If you have 'WaitForPort AMITCP' in your Startnet script you should know
if AmiTCP is running since any following commands won't execute unless
the port is up.

You could try resolving your providers address to test for a connection:

-----------------------------
failat 11
Inet:bin/resolve 158.152.1.65
if error
   echo "Not Connected"
else
   echo "Connected"
endif
-----------------------------

Phil.
-- 
Philip Stokes                                    phil@stokes.demon.co.uk
Hertfordshire
England