Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!snorkelwacker.mit.edu!stanford.edu!agate!usenet.ins.cwru.edu!ysub!temngt23
From: TEMNGT23@ysub.ysu.edu (Lou Anschuetz)
Newsgroups: comp.sys.ncr
Subject: Re: Finding out if TCP/IP is up
Message-ID: <91136.082236TEMNGT23@ysub.ysu.edu>
Date: 16 May 91 12:22:36 GMT
References: <91130.081040TEMNGT23@ysub.ysu.edu>
 <1991May13.174301.1651@NCoast.ORG> <91134.081431TEMNGT23@ysub.ysu.edu>
 <1991May15.142242.3193@NCoast.ORG>
Organization: Youngstown State University VM system (YSUB)
Lines: 37

In article <1991May15.142242.3193@NCoast.ORG>, jeffl@NCoast.ORG (Jeff Leyser)
says:
>If all the processes are still up, but you can't ping through loopback or
>through ethernet, it's a good bet your STREAMS drivers are screwed up.  This
>would also jibe with your remark about WIN-TCP requesting a whole bunch of
>STREAMS buffers.  Two things you can check -- see if the process inetinit is
>alive and well.  This process maintains the STREAMS drivers.  However, it is
>possible to have the processes running, and the drivers messed up.  DO NOT
>SIMPLY RESTART THE PROCESS.  You _MUST_ stop and start all of WIN_TCP.  If
>inetinit is up, and things still don't work, do what you are already doing --
>ping the loopback.  (Ping sends ICMP packets requesting an echo.  If you can't
>echo to yourself, either the "send" isn't going down to the loop, or the loop
>can't give ping the "recieve."  In either case, the drivers are screwed up.)
Following is the file I would like to execute from cron.  Looks like it
should work based on your comments.  Let me know if you see any problem.

/usr/etc/ping yfnserv 2 2 | grep "100% packet loss" >/dev/null
if [ "$?" -eq 0 ]
then
   /etc/init.d/win stop
   /etc/init.d/win start
   echo "WIN restarted" >> /tmp/neterror
fi
>
>
>However, all of this is nothing more than a patch.  You really need to
>_educate_ the users who are causing the crash.  Teach them what not to
>do, and tell them all the problems they are causing.  Otherwise, you'll
>be chasing your tail on this one for a long, long time.
Aye, there's the rub.  We have 3,000 users and add about 30 more per
week.  It's tough to make them all understand.  Changing the subject
just slightly - I understand SysV.4 does dynamic streams allocation,
thereby making this problem less likely to occur.  Any word on
SysV.4 for the tower line (anybody can respond here) ?
>--
Lou Anschuetz
temngt23@ysub.ysu.edu