From jkh@time.cdrom.com  Mon Nov 13 04:51:06 1995
Received: from time.cdrom.com (time.cdrom.com [192.216.222.226])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id EAA18105
          for <FreeBSD-gnats-submit@freebsd.org>; Mon, 13 Nov 1995 04:51:05 -0800
Received: (from jkh@localhost) by time.cdrom.com (8.6.12/8.6.9) id EAA19965; Mon, 13 Nov 1995 04:50:43 -0800
Message-Id: <199511131250.EAA19965@time.cdrom.com>
Date: Mon, 13 Nov 1995 04:50:43 -0800
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Reply-To: jkh@time.cdrom.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: Config doesn't properly trap signals
X-Send-Pr-Version: 3.2

>Number:         821
>Category:       kern
>Synopsis:       Config doesn't properly trap signals
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Nov 13 05:00:01 PST 1995
>Closed-Date:    Mon Oct 21 18:51:06 PDT 1996
>Last-Modified:  Mon Oct 21 18:51:30 PDT 1996
>Originator:     Jordan K. Hubbard
>Release:        FreeBSD 2.1-STABLE i386
>Organization:
Jordan
>Environment:

	2.1-STABLE

>Description:

Start the config of a kernel then interrupt it.  config will print:
Removing old directory ../../compile/MIMSY:  ^CFailed!
rm -rf ../../compile/MIMSY: Undefined error: 0

Clearly, "undefined error: 0" is the subprocess return status
after the signal was caught.
>How-To-Repeat:
See above.
>Fix:
Throw config out on its ear? :)

I mostly just note this so that I don't forget to eventually go
back and fix it.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: jkh 
State-Changed-When: Mon Oct 21 18:51:06 PDT 1996 
State-Changed-Why:  
This was fixed by changing the error message to a more generic 
"Failed!" 
>Unformatted:
