From owner-freebsd-bugs  Sun Mar 19 02:00:04 1995
Return-Path: bugs-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA00172 for bugs-outgoing; Sun, 19 Mar 1995 02:00:04 -0800
Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA00164; Sun, 19 Mar 1995 02:00:02 -0800
Date: Sun, 19 Mar 1995 02:00:02 -0800
Message-Id: <199503191000.CAA00164@freefall.cdrom.com>
From: J Wunsch <j@uriah.heep.sax.de>
Reply-To: J Wunsch <j@uriah.heep.sax.de>
To: freebsd-bugs
Subject: misc/254: fsck -p misbehaves for SIGQUIT
In-Reply-To: Your message of Sun, 19 Mar 1995 09:53:52 +0100
	<199503190853.JAA07997@uriah.heep.sax.de>
Sender: bugs-owner@FreeBSD.org
Precedence: bulk


>Number:         254
>Category:       misc
>Synopsis:       fsck -p misbehaves for SIGQUIT
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs (FreeBSD bugs mailing list)
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Mar 19 02:00:01 1995
>Originator:     & Wunsch
>Organization:
>Release:        FreeBSD 2.1.0-Development i386
>Environment:

-current as of CTM # 463

>Description:

Sending a SIGQUIT into the rc shell at startup time is expected to
complete the file system check and return to the single user shell.
fsck -p however aborts due to the SIGQUIT.

>How-To-Repeat:

Hit ^\ during system startup.

>Fix:
	
not yet known.


>Audit-Trail:
>Unformatted: