summaryrefslogtreecommitdiff
path: root/units
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2017-09-05 09:14:51 +0200
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2017-09-05 12:06:30 +0200
commit947d21171bdd8375db6482bc7d758d74b27f7dd4 (patch)
treef980340cb8459f11d07bb5f3864d5620e66d8777 /units
parent2f34bead2c896e1a056804bc50620d2e97a35c54 (diff)
downloadsystemd-947d21171bdd8375db6482bc7d758d74b27f7dd4.tar.gz
units: order cryptsetup-pre.target before cryptsetup.target
Normally this happens automatically, but if it happened that both targets were pulled in, even though there were no cryptsetup units, they could be started in reverse order, which would be somewhat confusing. Add an explicit ordering to avoid this potential issue.
Diffstat (limited to 'units')
-rw-r--r--units/cryptsetup-pre.target1
1 files changed, 1 insertions, 0 deletions
diff --git a/units/cryptsetup-pre.target b/units/cryptsetup-pre.target
index 65353419fc..42e35dd4e4 100644
--- a/units/cryptsetup-pre.target
+++ b/units/cryptsetup-pre.target
@@ -9,3 +9,4 @@
Description=Encrypted Volumes (Pre)
Documentation=man:systemd.special(7)
RefuseManualStart=yes
+Before=cryptsetup.target