summaryrefslogtreecommitdiff
path: root/units/remote-fs-pre.target
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2019-12-19 10:42:14 +0100
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2019-12-19 10:42:14 +0100
commit4186441bbd912dea9c8a43dfd19dcbea90b4c3a0 (patch)
tree120d01cbd0d3690652e46d03c244c4dc56d45fce /units/remote-fs-pre.target
parent7a670b1dd981c645064f69faf85b04620aadbafb (diff)
downloadsystemd-4186441bbd912dea9c8a43dfd19dcbea90b4c3a0.tar.gz
Revert "cryptsetup: umount encrypted devices before detaching it during shutdown"
This reverts commit 362c378291e85df3e00aaad491d1e08233ad127f. This commit introduced an ordering loop: remote-cryptsetup.target was both before and after remote-fs-pre.target. It also globally ordered all cryptsetup volumes before all mounts. Such global ordering is problematic if people have stacked storage. Let's look for a different solution. See https://github.com/systemd/systemd/pull/14378#discussion_r359460109.
Diffstat (limited to 'units/remote-fs-pre.target')
-rw-r--r--units/remote-fs-pre.target1
1 files changed, 0 insertions, 1 deletions
diff --git a/units/remote-fs-pre.target b/units/remote-fs-pre.target
index b4a68c73dd..3f22605c8c 100644
--- a/units/remote-fs-pre.target
+++ b/units/remote-fs-pre.target
@@ -11,4 +11,3 @@
Description=Remote File Systems (Pre)
Documentation=man:systemd.special(7)
RefuseManualStart=yes
-After=remote-cryptsetup.target