From owner-freebsd-bugs  Sun Mar  9 18:10:04 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA29329
          for bugs-outgoing; Sun, 9 Mar 1997 18:10:04 -0800 (PST)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA29321;
          Sun, 9 Mar 1997 18:10:02 -0800 (PST)
Date: Sun, 9 Mar 1997 18:10:02 -0800 (PST)
Message-Id: <199703100210.SAA29321@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Subject: Re: bin/2925: non-priviledged user can crash FreeBSD!! 
Reply-To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR bin/2925; it has been noted by GNATS.

From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
To: chern@tiger.towson.edu
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: bin/2925: non-priviledged user can crash FreeBSD!! 
Date: Sun, 09 Mar 1997 18:09:05 -0800

 > background running.  The system simply crashed and stopped.  I waited for 
 
 Are you *positive* that the system crashed, e.g. you tried to access
 it from another network node and it did not respond?  If you're
 running X and you run out of swap space, many times the system will
 shoot down the X server in its desparate attempt to find more memory
 resources.  Unfortunately, when the X server is shot unexpectedly like
 this it leaves the console in a bad state and it looks to the
 uninitiated like a system crash.  You must verify that it really *was*
 a system crash by seeing if the system is still up after you reproduce
 the failure.  Also, don't run an X server while testing these sorts of
 things - it only complicates the situation.  Thanks.
 
 					Jordan