[comp.sources.d] My System Keeps Crashing but Only When I Use NN

kellow@ndcheg.cheg.nd.edu (John Kellow) (07/10/89)

I've started using the NN newsreader posted recently and I think its 
great but I've been having this strange problem.  I normally read the
news through an rlogin session to the host that contains all of the
news and news software ( I don't use NNTP ).  Sometimes my connection
is abruptly closed.  It usually happens about half way through the display
of a new article.  In other words, I've finished reading one article
and I press the spacebar to see the next article and as the new article
is being displayed my terminal beeps and prints "Connection Closed" just
like when you normally terminate an rlogin session.  Now the weird part,
the first few times this happened the connection just closed, but lately
the entire computer reboots!  Other users report the same thing.  This 
has never happened before with any other program.  Just what does NN do
that other programs don't do?  Does it put the terminal in some weird
mode or something?  I know, since when can some program running on another
machine make another computer crash through an rlogin session - but believe
me it happens!  Has anybody else seen anything remotely similar?  If it
makes any difference the system that crashes is a Convergent Technologies
Miniframe running CTIX 3.2 (SYSV.2 w/ BSD 4.2 and 4.3 extensions).  I'd
really hate to have to stop using NN.  

John Kellow
kellow@ndcheg.cheg.nd.edu

maart@cs.vu.nl (Maarten Litmaath) (07/11/89)

kellow@ndcheg.cheg.nd.edu (John Kellow) writes:
\I've started using the NN newsreader posted recently and I think its 
\great but I've been having this strange problem.  I normally read the
\news through an rlogin session to the host that contains all of the
\news and news software ( I don't use NNTP ).  Sometimes my connection
\is abruptly closed.  It usually happens about half way through the display
\of a new article.  [...]

Check your tty and terminal modes WHILE NN IS BUSY, i.e. from some other
tty type:
	stty everything > /dev/tty01
or
	stty -a > /dev/tty01

if /dev/tty01 is the one your using NN on.
Interesting things are parity and the `nohang/clocal' bit.
If your terminal has a local setup key, you might find out easily how it
thinks to communicate with the host.
-- 
   "... a lap-top Cray-2 with builtin    |Maarten Litmaath @ VU Amsterdam:
cold fusion power supply"  (Colin Dente) |maart@cs.vu.nl, mcvax!botter!maart