Public bug reported:
The cryptsetup(8) manual page says (spurious lines omitted):
reencrypt <device> or --active-name <name> [<new_name>]
Run resilient reencryption (LUKS2 device only).
[...]
Reencryption process may be safely interrupted by a user via SIGTERM
signal (ctrl+c).
No: Control-C generates SIGINT.
System shutdown generates SIGTERM.
Nothing is said about the other two very similar signals:
SIGHUP Generated by logout (historically, by modem hanging up).
SIGQUIT Generated by control-\ (control-backslash).
I do not know if cryptsetup worries about those two signals or not.
Either way, the manual page should say something — in addition to
un-confusing SIGTERM and control-C (SIGINT); see signal(7).
N.b. To be pedantic, the keys which generate SIGINT and SIGQUIT
can be configured (see, e.g., stty(1)), however, ^C and ^\
are the most common (and default, I think).
Also, the package is technically "cryptsetup-bin" not "cryptsetup",
but Launchpad claims "'cryptsetup-bin' does not exist in Ubuntu."
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cryptsetup-bin 2:2.2.2-3ubuntu2.3
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Nov 20 18:15:03 2020
InstallationDate: Installed on 2020-10-19 (32 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: cryptsetup
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: cryptsetup (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905065
Title:
cryptsetup(8) man page confused about signals
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1905065/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
