[pkg-cryptsetup-devel] Bug#1010708: cryptsetup: init script doesn't appear to do anything with force-start due to masked systemd services

[Guilhem Moulin]

Control: severity -1 minor

On Sat, 07 May 2022 at 17:40:34 -0400, Andres Salomon wrote:
> Calling the init script with 'force-start' was how I used to start the
> volume and get prompted for a password, but on a newer system with
> systemd, that doesn't _appear_ to work any more:

The init scripts are masked by systemd but you should be able to run
`cryptdisks_start 8tb` or `systemd-cryptsetup at 8tb.service` to map the
volume.

> It would be good if /etc/init.d/cryptsetup either warned about the
> masked systemd service, and/or the cryptsetup postinst scripts
> deleted or prompted the user about the symlinks.

That would boil to overriding the systemd maintainers and I'm not going
to do that :-]

> Unless /etc/init.d/cryptsetup force-start is deprecated, of course!
> But README.Debian still describes using the init script.

Fair enough, I'll add a mention to systemd there.

-- 
Guilhem.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-cryptsetup-devel/attachments/20220805/14500146/attachment.sig>