Path: utzoo!attcan!uunet!abcfd20.larc.nasa.gov!uakari.primate.wisc.edu!bin
From: bin@primate.wisc.edu (Brain in Neutral)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Hughes LAT TCP/IP server crashes with task stack overflow error
Message-ID: <3130@uakari.primate.wisc.edu>
Date: 19 Sep 90 19:09:44 GMT
References: <1990Sep19.175648.17632@ucselx.sdsu.edu>
Sender: bin@primate.wisc.edu
Reply-To: bin@primate.wisc.edu
Lines: 16

From article <1990Sep19.175648.17632@ucselx.sdsu.edu>, by mccurdy@ucselx.sdsu.edu (mccurdy m):
> By the way - what happens is: something happens that causes the server to crash
> with a "task stack overflow" error, everyone on that server gets knocked off,
> and the server reloads. It seems to happen on all of the servers, we havn't been
> able to connect the crashes to any particular event. Hughes has provided us witha sniffer to assist in the detective work.

When I saw the problem, the crash occurred and the server reset.  The next day
it happened again, but the crash reoccurred every few minutes.  I got annoyed,
turned it off, turned it back on the next day and (of course) never saw the
problem again.  But by then I had switched the active terminals back to the
LocalNet and was not using the server for any "real" work.
--
Paul DuBois
dubois@primate.wisc.edu

                 "Was all of this because I wore a big man's hat?"