Bug#803356: cryptdisks conflicts with documentation, and is cryptic to use

[Michael Biebl]

control: reassign -1 release-notes

Hi Ian,

thanks for your bug report.

Am 29.10.2015 um 08:05 schrieb Ian Kelling:
> Package: systemd
> Version: 215-17+deb8u2
> 
> https://www.debian.org/releases/stable/amd64/install.txt.en says
> 
> "you will have to mount them manually after the boot" 
> ...
> "/etc/init.d/cryptdisks start"
> 
> In reality, this exits with success but does nothing.  Looking
> through the code, I find that the init.d does exit 0 and nothing
> else if parent pid != 1, unless the command is
> "reload."

Right, /etc/init.d/cryptdisks is a NOP under systemd. It's not started
during boot and trying to manually execute it will simply result in
nothing being done.
The reason for that is, that systemd has builtin cryptsetup support, so
the old sysv init script should not be run and therefor it has been
"masked" (it's a symlink to /dev/null)

This is basically a documentation problem, so I'm going to re-assign
this to the release-notes package.

This section should be clarified that the instructions are for sysvinit
only. It was probably copied over from previous releases where sysvinit
was still the default.


I think under systemd all you need to do is call "systemctl
daemon-reload" if you are doing changes to /etc/crypttab. This will re-run
/lib/systemd/system-generators/systemd-cryptsetup-generator

A few man pages which come in handy:
man systemd-cryptsetup-generator
man systemd-cryptsetup
man systemd-cryptsetup at .service

Regards,
Michael



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20151030/fba266fe/attachment-0002.sig>