From nobody  Sat Jan 24 10:14:31 1998
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA00695;
          Sat, 24 Jan 1998 10:14:31 -0800 (PST)
          (envelope-from nobody)
Message-Id: <199801241814.KAA00695@hub.freebsd.org>
Date: Sat, 24 Jan 1998 10:14:31 -0800 (PST)
From: akh@ariscom.com
To: freebsd-gnats-submit@freebsd.org
Subject: Any user can crash the system with a kill
X-Send-Pr-Version: www-1.0

>Number:         5560
>Category:       bin
>Synopsis:       Any user can crash the system with a kill
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jan 24 10:20:01 PST 1998
>Closed-Date:    Sat Jan 24 15:26:42 PST 1998
>Last-Modified:  Sat Jan 24 15:27:23 PST 1998
>Originator:     Aneche Fabrice
>Release:        2.2.5-RELEASE
>Organization:
Ariscom
>Environment:
FreeBSD kheops.inhouse.fr 2.2.5-RELEASE FreeBSD 2.2.5-RELEASE #0: Wed Jan 21 23:55:24 CET 1998     akh@kheops.inhouse.fr:/usr/src/sys/compile/KDell2  i386
>Description:
Any user with a user access and x started on the computer
>How-To-Repeat:
So start X with a startx command and in a xterm just type kill -9 -1
The system crash, it works on 225 release and 225 stable as 10 january.

 
>Fix:
No idea ...
>Release-Note:
>Audit-Trail:

From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
To: freebsd-gnats-submit@FreeBSD.ORG
Cc:  Subject: Re: bin/5560: Any user can crash the system with a kill 
Date: Sat, 24 Jan 1998 10:43:42 -0800

 [summary version of private email for gnats]
 
 It is not at all clear here that the system has actually crashed or
 simply the X server, leaving syscons in a bad state.  User should try
 to reach the box remotely via ethernet or serial terminal to verify
 that it is indeed "crashed."
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. 
>Unformatted:
