/etc/init.d/cryptdisks does not have a working 'start' option

[Trenton]

Release: Ubuntu 10.04.3 LTS (and possibly others)
Package Version: cryptsetup 2:1.1.0~rc2-1ubuntu13 (any possibly others)

It appears that the only way to manually start the cryptdisks service once it has been stopped is by using the restart or reload options (i.e. "service cryptdisks reload"). The /etc/init.d/cryptdisks script should include a start option that contains "do_start".

[Clint Byrum (clint-fewbar)]

Trenton thanks! Note that the workaround is to run

'start cryptdisks-enable'

This definitely is more intuitive though.

[Steve Langasek (vorlon)]

Note that the cryptdisks start option was deliberately removed; see bug #473615.

[Clint Byrum (clint-fewbar)]

Excerpts from Steve Langasek's message of Wed Aug 24 23:30:39 UTC 2011:
> Note that the cryptdisks start option was deliberately removed; see bug
> #473615.
>

Hm. So we're just stuck with a confusing situation until we can remove
the init.d script in favor of a pure upstart shutdown.

We could add a message on start to direct the user to the upstart
job with a warning that it may cause them issues.

[Trenton (trenton-ivey)]

That sounds like a good idea. Adding a simple "echo To start cryptdisks
use the \'restart\' option" would be helpful. Could this result in
confusing text at startup when the init.d script was run?

On 08/25/2011 12:53 PM, Clint Byrum wrote:
> Excerpts from Steve Langasek's message of Wed Aug 24 23:30:39 UTC 2011:
>> Note that the cryptdisks start option was deliberately removed; see bug
>> #473615.
>>
> Hm. So we're just stuck with a confusing situation until we can remove
> the init.d script in favor of a pure upstart shutdown.
>
> We could add a message on start to direct the user to the upstart
> job with a warning that it may cause them issues.
>

[Dave Walker (davewalker)]

Un-subscribing ~ubuntu-sponsors as there is nothing currently that needs sponsoring, if this changes please re-subscribe ~ubuntu-sponsors, thanks