On Mon, Jun 16, 2008 at 4:38 PM, Theodore Tso <[EMAIL PROTECTED]> wrote:
> On Sat, Jun 14, 2008 at 09:02:01PM +0200, David wrote:
>> Package: e2fsprogs
>> Version: 1.40.8-2
>> Severity: wishlist
>>
>> 1) Let users cleanly interrupt fsck
>>
>> If users hit ctrl+c (or maybe ESC), fsck should guarantee that the
>> filesystem is in a relatively safe state before terminating.
>>
>> fsck probably does do this already, but some users on the threads
>> weren't sure, and thought that hitting ctrl+C might be an unsafe
>> operation.
>
> "man e2fsck.conf". Short version; place in /etc/e2fsck.conf:
>
> [options]
> allow_cancelation = true
>
> At this point, it is up to whatever system (sysvinit, upstart),
> etc. to allow a ^C to be passed to the fsck process, but as long as it
> receives a SIGINT signal, it will do the right thing.
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 :-/
Here is my /etc/e2fsck.conf:
=====
[options]
buggy_init_scripts = 1
allow_cancellation = 1
=====
My version has an extra "l" in cancellation, because that's how it is
spelled in the man page. The buggy_init_scripts line was there by
default.
Is this behaviour a bug in sysvinit or in fsck? Is there anything else
I should check?
David.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
