[Pkg-cryptsetup-devel] Bug#476425: cryptsetup: Incorrect rc script settings (start instead of stop in runlevels 0, 6)

grunge blaha at tipsport.cz
Wed Apr 16 16:45:06 UTC 2008


Package: cryptsetup
Version: 2:1.0.6~pre1+svn45-1
Severity: important


/etc/init.d/crypdisks and /etc/init.d/cryptdisks-eary get only started,
first on boot in runlevel S and then again on shutdown in runlevels 0
and 6.  This doesn't match comments in those scripts and leaves their
stop actions unused. The cause seems in cryptsetup's postinst script,
which says:

update-rc.d cryptdisks-early start 26 S . start 59 0 6 .
update-rc.d cryptdisks start 28 S . start 48 0 6 .

I think there should be "stop" instead of the second "start" on both
lines. This part of postinst seems generated by debhelper, so the real
cause may be somewhere else (source's debian/rules; didn't look there).

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.24.4 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=en_US.UTF8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages cryptsetup depends on:
ii  dmsetup                      2:1.02.24-4 The Linux Kernel Device Mapper use
ii  libc6                        2.7-10      GNU C Library: Shared libraries
ii  libdevmapper1.02.1           2:1.02.24-4 The Linux Kernel Device Mapper use
ii  libpopt0                     1.10-3      lib for parsing cmdline parameters
ii  libuuid1                     1.40.8-2    universally unique id library

cryptsetup recommends no packages.

-- no debconf information





More information about the Pkg-cryptsetup-devel mailing list