No subject

failed, or the route, or is the system too loaded to answer?  Has the
system crashed?  Hard to tell.  traceroute might help you detect routing
problems per se, or might not.  ping can be useful as well.  However, it
is >>really hard<< to detect a remote network interface failure per se
-- there are multiple possible causes to a failure in communications,
and any one of them might appear to be a "dead" socket.

If you were really asking for the names of tools like route, ifconfig
and so forth I'd recommend that you consider buying a good book on Unix
or Linux systems administration, since most of them are described in
detail therein.

  rgb

> 
> Thanks.
> 
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Sports - live college hoops coverage
> http://sports.yahoo.com/
> _______________________________________________
> Beowulf mailing list, Beowulf at beowulf.org
> To change your subscription (digest mode or unsubscribe) visit http://www.beowulf.org/mailman/listinfo/beowulf
> 

-- 
Robert G. Brown	                       http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567  Fax: 919-660-2525     email:rgb at phy.duke.edu