From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Benjamin Marzinski" Subject: [PATCH v2 16/18] multipathd.service: remove blk-availability Requires Date: Thu, 7 Apr 2016 18:20:10 -0500 Message-ID: <1460071212-21018-17-git-send-email-bmarzins@redhat.com> References: <1460071212-21018-1-git-send-email-bmarzins@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1460071212-21018-1-git-send-email-bmarzins@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: device-mapper development Cc: Christophe Varoqui List-Id: dm-devel.ids multipathd.service can start up and run just fine without blk-availability.service. It is only necessary to coordinate shutdown order in certain multipath setups (over iscsi for instance). Thus, instead of "Requires", multipathd.service should use "Wants" Signed-off-by: Benjamin Marzinski --- multipathd/multipathd.service | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/multipathd/multipathd.service b/multipathd/multipathd.service index fc2e009..d5f8606 100644 --- a/multipathd/multipathd.service +++ b/multipathd/multipathd.service @@ -1,11 +1,10 @@ [Unit] Description=Device-Mapper Multipath Device Controller -Requires=blk-availability.service Before=iscsi.service iscsid.service lvm2-activation-early.service Before=local-fs-pre.target After=multipathd.socket DefaultDependencies=no -Wants=local-fs-pre.target multipathd.socket +Wants=local-fs-pre.target multipathd.socket blk-availability.service Conflicts=shutdown.target [Service] -- 1.8.3.1