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.

diff --git a/system-preset/90-systemd.preset b/system-preset/90-systemd.preset
index 3ba4bb760df9a73b143e30407e1429666110a2bb..98bc4c3c55ad834b10b3ad76981e1ef27351e62f 100644 (file)
--- a/system-preset/90-systemd.preset
+++ b/system-preset/90-systemd.preset
@@ -9,6 +9,7 @@
 # generally follow a default-off policy.
 
 enable remote-fs.target
+enable remote-cryptsetup.target
 enable machines.target
 
 enable getty@.service

diff --git a/units/remote-cryptsetup.target b/units/remote-cryptsetup.target
index 60943bd1cbc1bc06220d6567593b2da296b3bcc5..c306d521f711fa58d3692bc7a4e65f7936e82ea5 100644 (file)
--- 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