Debian bug report logs - #835
syslogd dies, leaves system unfixable

Message received at debian-bugs:

From arlut.utexas.edu!grib Mon Apr 24 08:20:45 1995
Return-Path: <grib@arlut.utexas.edu>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0s3PwK-0004wKC; Mon, 24 Apr 95 08:20 PDT
Received: from ns1.arlut.utexas.edu by pixar.com with SMTP id AA29474
  (5.65c/IDA-1.4.4 for <debian-bugs@pixar.com>); Mon, 24 Apr 1995 08:20:41 -0700
Received: from mamba.arlut.utexas.edu (mamba.arlut.utexas.edu [129.116.176.42]) by ns1.arlut.utexas.edu (8.6.11/8.6.9) with SMTP id KAA09664 for <debian-bugs@pixar.com>; Mon, 24 Apr 1995 10:20:37 -0500
Received: by mamba.arlut.utexas.edu (5.x/SMI-SVR4)
	id AA22626; Mon, 24 Apr 1995 10:20:48 -0500
From: grib@arlut.utexas.edu (William Gribble)
Message-Id: <9504241520.AA22626@mamba.arlut.utexas.edu>
Subject: syslogd dies, leaves system unfixable
To: debian-bugs@pixar.com
Date: Mon, 24 Apr 1995 10:20:48 -0600 (CDT)
X-Mailer: ELM [version 2.4 PL22]
Content-Type: text

package: sysklogd
version: 1.2-9

My SLIP connection is prone to be disconnected.  When this happens, the 
SLIP driver starts generating large numbers of error messages of the 
form (not exact, I don't have a logfile handy)

SLIP: sl0: transmit timed out: bad line quality?

After a few thousand of these (I have a ping -i 60 running to keep my 
connection alive, and it keeps on ticking after the connection goes bad)
syslogd stops accepting connections.  

This is a Bad Thing, since any logins or su's hang up since they can't 
connect to syslogd.   If I don't have a root window open on the machine,
the only solution is to ctrl-alt-del, and even that doesn't work quite 
right (I have to repeatedly ctrl-alt-del to get through the steps of the
shutdown process).

Bill Gribble