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

[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 simply be disabled during parallel startup,
and I am making that change.

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 *not*
be considered a failure of the init script.  Please squash exit code
32 in these init scripts.

Ben.

-- System Information:
Debian Release: squeeze/sid
  APT prefers proposed-updates
  APT policy: (500, 'proposed-updates'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages initscripts depends on:
ii  coreutils                     8.5-1      GNU core utilities
ii  debianutils                   3.4.2+nmu1 Miscellaneous utilities specific t
ii  libc6                         2.11.2-7   Embedded GNU C Library: Shared lib
ii  lsb-base                      3.2-26     Linux Standard Base 3.2 init scrip
ii  mount                         2.17.2-3.3 Tools for mounting and manipulatin
ii  sysv-rc                       2.88dsf-13 System-V-like runlevel change mech
ii  sysvinit-utils                2.88dsf-13 System-V-like utilities

Versions of packages initscripts recommends:
ii  e2fsprogs                     1.41.12-2  ext2/ext3/ext4 file system utiliti
ii  psmisc                        22.13-1    utilities that use the proc file s

initscripts suggests no packages.

-- no debconf information