Subject: Re: bin/21658 (interrupting (^C) /etc/rc.d/fsck doesn't stop auto boot)
To: None <lukem@NetBSD.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org,>
From: ITOH Yasufumi <itohy@NetBSD.org>
List: netbsd-bugs
Date: 12/15/2006 15:55:02
The following reply was made to PR bin/21658; it has been noted by GNATS.
From: itohy@NetBSD.org (ITOH Yasufumi)
To: gnats-bugs@NetBSD.org
Cc: lukem@NetBSD.org, netbsd-bugs@NetBSD.org, gnats-admin@NetBSD.org,
tsutsui@NetBSD.org
Subject: Re: bin/21658 (interrupting (^C) /etc/rc.d/fsck doesn't stop auto boot)
Date: Sat, 16 Dec 2006 00:53:38 +0900
In article <20061126013856.C6FB663B8C1@narn.NetBSD.org>
tsutsui@netbsd.org writes:
> State-Changed-From-To: open->feedback
> State-Changed-By: tsutsui@netbsd.org
> State-Changed-When: Sun, 26 Nov 2006 10:38:55 +0900
> State-Changed-Why:
> Is this the same problem with PR misc/29822, which has been closed?
That PR describes only a subset of this PR.
I tested current (20061204 build) userland.
- ^C stops fsck and bring to single user, but the /etc/rc.d/fsck
script doesn't print "Boot interrupted." message since the
exit code of fsck is not properly set.
- ^\ doesn't wait for current check to finish, but fall to
single user immediately, leaving orphaned fsck_* processes
running.
As I analyzed, I think fsck (the frontend) should be modified to
handle the keyboard interrupts.
--
ITOH Yasufumi