From owner-freebsd-bugs Sat Jan 24 10:50:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03049 for freebsd-bugs-outgoing; Sat, 24 Jan 1998 10:50:02 -0800 (PST) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: (from gnats@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03041; Sat, 24 Jan 1998 10:50:01 -0800 (PST) (envelope-from gnats) Date: Sat, 24 Jan 1998 10:50:01 -0800 (PST) Message-Id: <199801241850.KAA03041@hub.freebsd.org> To: freebsd-bugs Cc: From: "Jordan K. Hubbard" Subject: Re: bin/5560: Any user can crash the system with a kill Reply-To: "Jordan K. Hubbard" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/5560; it has been noted by GNATS. From: "Jordan K. Hubbard" 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."