From: Martin Wilck Date: Tue, 23 May 2023 10:43:46 +0000 (+0200) Subject: fabrics: fix conditions in nvmf-autoconnect.service X-Git-Tag: v2.5~100 X-Git-Url: https://www.infradead.org/git/?a=commitdiff_plain;h=9803d92f073a4c8c398de05e6edb408565d8faf9;p=users%2Fsagi%2Fnvme-cli.git fabrics: fix conditions in nvmf-autoconnect.service The unit should be started if either config.json or discovery.conf exists. The current syntax would start it if either one does not exist. Fix it. Fixes: eec7634 ("fabrics: Trigger auto connect if config.json exists") Signed-off-by: Martin Wilck --- diff --git a/nvmf-autoconnect/systemd/nvmf-autoconnect.service.in b/nvmf-autoconnect/systemd/nvmf-autoconnect.service.in index c57ff718..06790c30 100644 --- a/nvmf-autoconnect/systemd/nvmf-autoconnect.service.in +++ b/nvmf-autoconnect/systemd/nvmf-autoconnect.service.in @@ -1,7 +1,7 @@ [Unit] Description=Connect NVMe-oF subsystems automatically during boot -ConditionPathExists=|!@SYSCONFDIR@/nvme/config.json -ConditionPathExists=|!@SYSCONFDIR@/nvme/discovery.conf +ConditionPathExists=|@SYSCONFDIR@/nvme/config.json +ConditionPathExists=|@SYSCONFDIR@/nvme/discovery.conf After=network-online.target Before=remote-fs-pre.target