On Sun, Jun 22, 2008 at 2:55 PM, Theodore Tso <[EMAIL PROTECTED]> wrote: > On Fri, Jun 20, 2008 at 12:04:23AM +0200, David wrote: >> I just tested this, and it doesn't seem to work for me :-/ (that's why >> I'm CC-ing the bug). >> >> As before, hitting Ctrl+C does interrupt the / fsck, and the boot >> continues. However, the root filesystem remains readonly, my system >> has a lot of bootup errors and the bootup process takes a long time, >> forcing me to reboot again and let the / fsck finish. It's a nasty DoS >> condition :-/ > > That sounds like it's a problem with sysvinit scripts; its not the > responsibility of e2fsck to remount the filesystem read-write. I'm > guessing the ^C managed to interrupt the sysvinit scripts as well as > the fsck program. >
Thanks, this does seem to be the case. I tested fsck on the command-line, and it correctly handles Ctrl+C (prints Interrupted, and exits with 0 code). So it is capturing Ctrl+C, at least when e2fsck is in control of the terminal. I assume that sysvinit is running the root fsck init script in the background, and when I hit Ctrl+C, sysvinit terminates the init script along with fsck. I've posted an update to my sysvinit bug report. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
