| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | units/blockdev@.target: conflict with umount.target | Mike Yuan | 2023-09-27 | 1 | -0/+4 |
| | | | | | | | | | | | | | | | | Follow-up for d120ce478dc0043c89899799b5c1aaf62901bea9 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 | ||||
| * | units: don't stop blockdev@.target unit at shutdown | Lennart Poettering | 2023-06-01 | 1 | -0/+1 |
| | | | | | | | | | | | | 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. | ||||
| * | license: LGPL-2.1+ -> LGPL-2.1-or-later | Yu Watanabe | 2020-11-09 | 1 | -1/+1 |
| | | |||||
| * | units: introduce blockdev@.target for properly ordering mounts/swaps against ↵ | Lennart Poettering | 2020-01-21 | 1 | -0/+13 |
| cryptsetup Let's hook it into both cryptsetup-generator and gpt-auto-generator with a shared implementation in generator.c Fixes: #8472 | |||||
 |
index : systemd | |
| systemd | Fast-forward packages |
| summaryrefslogtreecommitdiffstats |