Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!rex!uflorida!gatech!usenet.ins.cwru.edu!ncoast!jeffl
From: jeffl@NCoast.ORG (Jeff Leyser)
Newsgroups: comp.sys.ncr
Subject: Re: Finding out if TCP/IP is up
Message-ID: <1991May13.174301.1651@NCoast.ORG>
Date: 13 May 91 17:43:01 GMT
References: <91130.081040TEMNGT23@ysub.ysu.edu>
Organization: North Coast Public Access Un*x (ncoast)
Lines: 26

In post <91130.081040TEMNGT23@ysub.ysu.edu>, Lou Anschuetz <TEMNGT23@ysub.ysu.edu> says:
!!I have an NCR Tower 700 with 16MB of memory.  All my users come in
!!through the Ethernet board via a terminal server.  It is possible
!!for certain dialup users (Commodore 64 in fact) to reboot their
!!machines while still on line.  Since this "information" is just
!!passed down the pipeline to the tower, it attempts to handle this
!!by allocating thousands of 2k streams.  I am already set at maximum

First off, I don't understand this at all.  What "information" is being
sent down what "line?"
!!What I need, therefore, is a way to determine if TCP/IP is up
!!from cron.  If it is not I can do a win restart (a little

Several things, depending on how WIN crashed:

A) Grep through a ps -aef and look for tcplisten, inetinit, and listen
(if you have listen configured to run at all)

B) Look at the output of an ifconfig.  Maybe WIN is marking the
interface as down.

C) run a netstat in the background, with it's output going to a file.
check the file for data.  If there is no data after a reasonable time,
kill the netstat, and assume WIN is hosed.
-- 
Jeff Leyser                                     jeffl@NCoast.ORG