diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2017-10-12 22:34:54 +0200 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2017-10-17 19:15:58 +0200 |
| commit | a0dd209763f9e67054ee322a2dfd52bccf345c2e (patch) | |
| tree | a67ab30eb04806e760603ea0fd1f858f0d51a043 /units/remote-cryptsetup.target | |
| parent | units: add [Install] section to remote-cryptsetup.target (diff) | |
| download | systemd-a0dd209763f9e67054ee322a2dfd52bccf345c2e.tar.xz systemd-a0dd209763f9e67054ee322a2dfd52bccf345c2e.zip | |
units: replace remote-cryptsetup-pre.target with remote-fs-pre.target
remote-cryptsetup-pre.target was designed as an active unit (that pulls in
network-online.target), the opposite of remote-fs-pre.target (a passive unit,
with individual provider services ordering itself before it and pulling it in,
for example iscsi.service and nfs-client.target).
To make remote-cryptsetup-pre.target really work, those services should be
ordered before it too. But this would require updates to all those services,
not just changes from systemd side.
But the requirements for remote-fs-pre.target and remote-cryptset-pre.target
are fairly similar (e.g. iscsi devices can certainly be used for both), so
let's reuse remote-fs-pre.target also for remote cryptsetup units. This loses
a bit of flexibility, but does away with the requirement for various provider
services to know about remote-cryptsetup-pre.target.
Diffstat (limited to 'units/remote-cryptsetup.target')
| -rw-r--r-- | units/remote-cryptsetup.target | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/units/remote-cryptsetup.target b/units/remote-cryptsetup.target index c306d521f7..d485b06726 100644 --- a/units/remote-cryptsetup.target +++ b/units/remote-cryptsetup.target @@ -8,7 +8,7 @@ [Unit] Description=Remote Encrypted Volumes Documentation=man:systemd.special(7) -After=remote-cryptsetup-pre.target +After=remote-fs-pre.target DefaultDependencies=no Conflicts=shutdown.target |