Your message dated Thu, 23 Aug 2012 03:25:37 +0100
with message-id 
<CANBHLUja8Dj9XYdP9_NSEp-7Ck86ArDs9YeGWy_we=tr2z7...@mail.gmail.com>
and subject line crazy talk
has caused the Debian Bug report #685242,
regarding cryptsetup does not stop =)
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.)


-- 
685242: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685242
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cryptsetup
Version: 2:1.4.3-2

Either there is a typo, or it is doing something very interesting.

In the debian/rules there are following lines:

        dh_installinit -a --no-start --name=cryptdisks-early
--update-rcd-params="start 26 S . start 59 0 6 ."
        dh_installinit -a --no-start --name=cryptdisks
--update-rcd-params="start 28 S . start 48 0 6 ."

Which I interpret as:

* Start with sequence number [26/28] in single user mode
* Start with sequence number [59/48] at halt and reboot

But when do they stop? Never? Then why there is do_stop in crypdisks.functions.

If it's a typo and it should be "stop [59/48] 0 6 ." please fix it.

If everything is correct please explain your black init magic =)

Regards,

Dmitrijs.

--- End Message ---
--- Begin Message ---
>From #debian-mentors I got advice on the Policy,

http://www.debian.org/doc/debian-policy/ch-opersys.html#s-sysvinit

9.3.1.

The two runlevels 0 (halt) and 6 (reboot) are slightly different. In
these runlevels, the links with an S prefix are still called after
those with a K prefix, but they too are called with the single
argument stop.

--- End Message ---

Reply via email to