Hi,
First of all, as a workaround to be able to ^C fsck while not in repair mode,
one can add the following in /etc/e2fsck.conf:
[options]
allow_cancellation = true
This forces fsck to return with zero and postpone the check for the next boot.
But of course that doesn't solve the problem
On 2010-09-12 12:22 +0200, Kel Modderman wrote:
> On Saturday 04 September 2010 06:39:49 Goswin von Brederlow wrote:
>> Package: insserv
>> Version: 1.14.0-2
>> Severity: critical
>>
>> Hi,
>>
>> during boot /etc/rcS.d/S13checkfs.sh starts a filesystem check (hasn't
>> been checked for 197 days)
> Hi!
>
> I encountered this bug, too.
>
>>How does changing /etc/init.d/rc with the below patch modify behaviour?
> No, Kel, nothing changed. Sorry.
When I observed boot after modifying the signal trap, CTRL-C did not truncate
startpar's execution of boot scripts in runlevel S. I wonder why you
c
Hi!
I encountered this bug, too.
>How does changing /etc/init.d/rc with the below patch modify behaviour?
No, Kel, nothing changed. Sorry.
--
Regards,
Alexander Batischev
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact li
Kel Modderman writes:
> On Saturday 04 September 2010 06:39:49 Goswin von Brederlow wrote:
>> Package: insserv
>> Version: 1.14.0-2
>> Severity: critical
>>
>> Hi,
>>
>> during boot /etc/rcS.d/S13checkfs.sh starts a filesystem check (hasn't
>> been checked for 197 days) as well as giving some e
On Saturday 04 September 2010 06:39:49 Goswin von Brederlow wrote:
> Package: insserv
> Version: 1.14.0-2
> Severity: critical
>
> Hi,
>
> during boot /etc/rcS.d/S13checkfs.sh starts a filesystem check (hasn't
> been checked for 197 days) as well as giving some errors for missing
> devices. Since
Sven Joachim writes:
> reassign 595431 sysvinit-utils
> found 595431 2.88-12
> thanks
>
> On 2010-09-03 22:39 +0200, Goswin von Brederlow wrote:
>
>> Package: insserv
>> Version: 1.14.0-2
>> Severity: critical
>>
>> Hi,
>>
>> during boot /etc/rcS.d/S13checkfs.sh starts a filesystem check (hasn't
On Fri, 03 Sep 2010, Petter Reinholdtsen wrote:
> [Sven Joachim]
> > I think Ctrl-c should just abort the fsck and continue the boot
> > (this happens here with CONCURRENCY=none in /etc/default/rcS, but I
> > don't have any actual filesystem problems and booted with the
> > forcefsck option). Anyw
[Sven Joachim]
> I think Ctrl-c should just abort the fsck and continue the boot
> (this happens here with CONCURRENCY=none in /etc/default/rcS, but I
> don't have any actual filesystem problems and booted with the
> forcefsck option). Anyway, this seems to be a bug in startpar's
> signal handling
reassign 595431 sysvinit-utils
found 595431 2.88-12
thanks
On 2010-09-03 22:39 +0200, Goswin von Brederlow wrote:
> Package: insserv
> Version: 1.14.0-2
> Severity: critical
>
> Hi,
>
> during boot /etc/rcS.d/S13checkfs.sh starts a filesystem check (hasn't
> been checked for 197 days) as well as
Package: insserv
Version: 1.14.0-2
Severity: critical
Hi,
during boot /etc/rcS.d/S13checkfs.sh starts a filesystem check (hasn't
been checked for 197 days) as well as giving some errors for missing
devices. Since I didn't want to wait for the fsck before fixing the
missing devices I aborted the c
11 matches
Mail list logo
