From owner-freebsd-bugs  Sat Jan 24 15:28:04 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA22212
          for freebsd-bugs-outgoing; Sat, 24 Jan 1998 15:28:04 -0800 (PST)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22190;
          Sat, 24 Jan 1998 15:27:48 -0800 (PST)
          (envelope-from jkh@FreeBSD.org)
From: "Jordan K. Hubbard" <jkh@FreeBSD.ORG>
Received: (from jkh@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id PAA23094;
	Sat, 24 Jan 1998 15:27:22 -0800 (PST)
Date: Sat, 24 Jan 1998 15:27:22 -0800 (PST)
Message-Id: <199801242327.PAA23094@freefall.freebsd.org>
To: akh@ariscom.com, jkh@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG
Subject: Re: bin/5560
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: Any user can crash the system with a kill

State-Changed-From-To: open-closed
State-Changed-By: jkh
State-Changed-When: Sat Jan 24 15:26:42 PST 1998
State-Changed-Why: 
User was indeed incorrect about the nature of the problem - he shot
down his X server with a signal 9 and so it did the obvious thing of
leaving the console in a highly hosed state.  System is still actually
running fine and has not crashed.