Bug#608534: [Pkg-sysvinit-devel] Bug#608534: fsck exit code 32 should be treated as success

2011-01-08 Thread Kel Modderman
tags 608534 patch thanks On Saturday 01 January 2011 19:29:42 Petter Reinholdtsen wrote: > [Ben Hutchings] > > However, check{root,fsck}.sh are interactive and fsck will be and > > should be interruptible. If fsck checks the filesystem only due to > > a schedule (number of days or number of mount

Bug#608534: fsck exit code 32 should be treated as success

2011-01-01 Thread Petter Reinholdtsen
[Ben Hutchings] > However, check{root,fsck}.sh are interactive and fsck will be and > should be interruptible. If fsck checks the filesystem only due to > a schedule (number of days or number of mounts since last check) and > not due to a detected error condition then a user interrupt should > *no

Bug#608534: fsck exit code 32 should be treated as success

2010-12-31 Thread Ben Hutchings
Package: initscripts Version: 2.88dsf-13 Severity: important Bug #582442 concerns the ability to interrupt init scripts and in particular fsck. startpar may run multiple non-interactive scripts in parallel and currently the user may unintentionally interrupt multiple scripts. SIGINT should simpl