4 Commits

Author	SHA1	Message	Date
Mike Yuan	99f360a46b	units/blockdev@.target: conflict with umount.target ... Follow-up for d120ce478d blockdev@.target is used as a synchronization point between the mount unit and corresponding systemd-cryptsetup@.service. After the mentioned commit, it doesn't get a stop job enqueued during shutdown, and thus the stop job for systemd-cryptsetup@.service could be run before the mount unit is stopped. Therefore, let's make blockdev@.target conflict with umount.target, which is also what systemd-cryptsetup@.service does. Fixes #29336	2023-09-27 12:33:40 +02:00
Lennart Poettering	d120ce478d	units: don't stop blockdev@.target unit at shutdown ... We want that cryptsetup/veritysetup devices can stick around until the very end, as well as the users of them which might depend on blockdev@.target for the devices. Hence leave the targets around till the very end. Note that their runtime is managed via StopWhenUnneeded= anyway, hence unless their are volumes that actually survive still the very end they target units will still be stopped.	2023-06-01 18:49:43 +02:00
Yu Watanabe	db9ecf0501	license: LGPL-2.1+ -> LGPL-2.1-or-later	2020-11-09 13:23:58 +09:00
Lennart Poettering	a7e8855879	units: introduce blockdev@.target for properly ordering mounts/swaps against cryptsetup ... Let's hook it into both cryptsetup-generator and gpt-auto-generator with a shared implementation in generator.c Fixes: #8472	2020-01-21 20:23:13 +01:00