Your message dated Sun, 8 Jun 2008 16:42:53 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: [Pkg-cryptsetup-devel] Bug#476425: cryptsetup: Incorrect
rc script settings (start instead of stop in runlevels 0, 6)
has caused the Debian Bug report #476425,
regarding cryptsetup: Incorrect rc script settings (start instead of stop in
runlevels 0, 6)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
476425: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476425
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
On 16/04/2008 grunge wrote:
> /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).
no, it's correct that way. please the links that are actually created:
$ ls -l /etc/rc*.d/*cryptdisks*
lrwxrwxrwx 1 root root 20 2008-05-30 12:13 /etc/rc0.d/K17cryptdisks ->
../init.d/cryptdisks
lrwxrwxrwx 1 root root 26 2008-05-30 12:13 /etc/rc0.d/K19cryptdisks-early ->
../init.d/cryptdisks-early
lrwxrwxrwx 1 root root 20 2008-05-30 12:13 /etc/rc6.d/K17cryptdisks ->
../init.d/cryptdisks
lrwxrwxrwx 1 root root 26 2008-05-30 12:13 /etc/rc6.d/K19cryptdisks-early ->
../init.d/cryptdisks-early
lrwxrwxrwx 1 root root 26 2008-06-03 14:17 /etc/rcS.d/S09cryptdisks-early ->
../init.d/cryptdisks-early
lrwxrwxrwx 1 root root 20 2008-06-03 14:17 /etc/rcS.d/S11cryptdisks ->
../init.d/cryptdisks
i agree that the way sysvinit manages this is confusing, but that's the
way it is. please see sysvinit documentation for more information.
greetings,
jonas
--- End Message ---
