summaryrefslogtreecommitdiff
path: root/units/remote-cryptsetup.target
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2017-10-12 22:13:03 +0200
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2017-10-13 08:03:16 +0200
commit8f462b074eb9830d6d5029f70c9010ce50e68357 (patch)
tree63eef3fd44707befe37e87b6146931d2403b5e27 /units/remote-cryptsetup.target
parent4e93d369b9f80c9f253f75bd65135705fbdf2806 (diff)
downloadsystemd-8f462b074eb9830d6d5029f70c9010ce50e68357.tar.gz
units: add [Install] section to remote-cryptsetup.target
This makes this target the same as remote-fs.target in this regard. In practice it probably doesn't make that much difference, because all encrypted devices that are part of remote-fs.target (marked with _netdev) will be used for mount points, so they will be pulled in anyway individually, but with this change any such device will be configured, even if it is not pulled by any other unit.
Diffstat (limited to 'units/remote-cryptsetup.target')
-rw-r--r--units/remote-cryptsetup.target6
1 files changed, 6 insertions, 0 deletions
diff --git a/units/remote-cryptsetup.target b/units/remote-cryptsetup.target
index 60943bd1cb..c306d521f7 100644
--- a/units/remote-cryptsetup.target
+++ b/units/remote-cryptsetup.target
@@ -8,3 +8,9 @@
[Unit]
Description=Remote Encrypted Volumes
Documentation=man:systemd.special(7)
+After=remote-cryptsetup-pre.target
+DefaultDependencies=no
+Conflicts=shutdown.target
+
+[Install]
+WantedBy=multi-user.target