anitazha / rpms / systemd

Forked from rpms/systemd 3 years ago
Clone

Blame SOURCES/0533-units-order-cryptsetup-pre.target-before-cryptsetup..patch

ecbff1
From acf59b657e23e3b5b0f038823fe57dcfb4f914a4 Mon Sep 17 00:00:00 2001
ecbff1
From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= <zbyszek@in.waw.pl>
ecbff1
Date: Tue, 5 Sep 2017 09:14:51 +0200
ecbff1
Subject: [PATCH] units: order cryptsetup-pre.target before cryptsetup.target
ecbff1
ecbff1
Normally this happens automatically, but if it happened that both targets were
ecbff1
pulled in, even though there were no cryptsetup units, they could be started
ecbff1
in reverse order, which would be somewhat confusing. Add an explicit ordering
ecbff1
to avoid this potential issue.
ecbff1
ecbff1
Cherry-picked from: 947d21171bdd8375db6482bc7d758d74b27f7dd4
ecbff1
Resolves: #1384014
ecbff1
---
ecbff1
 units/cryptsetup-pre.target | 1 +
ecbff1
 1 file changed, 1 insertion(+)
ecbff1
ecbff1
diff --git a/units/cryptsetup-pre.target b/units/cryptsetup-pre.target
ecbff1
index 65353419f..42e35dd4e 100644
ecbff1
--- a/units/cryptsetup-pre.target
ecbff1
+++ b/units/cryptsetup-pre.target
ecbff1
@@ -9,3 +9,4 @@
ecbff1
 Description=Encrypted Volumes (Pre)
ecbff1
 Documentation=man:systemd.special(7)
ecbff1
 RefuseManualStart=yes
ecbff1
+Before=cryptsetup.target