fabrics: autoconnect: explicitly express module dependency

Use Wants/After to let systemd handle loading the kernel module, which
is the preferred way.

Signed-off-by: Daniel Wagner <dwagner@suse.de>

diff --git a/nvmf-autoconnect/systemd/nvmf-autoconnect.service.in b/nvmf-autoconnect/systemd/nvmf-autoconnect.service.in
index 621879a5f04b99d15caea83a8a40c7ba6b6f5223..92960cde6144fcc98d23ee8a491a86abc179480d 100644 (file)
--- a/nvmf-autoconnect/systemd/nvmf-autoconnect.service.in
+++ b/nvmf-autoconnect/systemd/nvmf-autoconnect.service.in
@@ -2,12 +2,13 @@
 Description=Connect NVMe-oF subsystems automatically during boot
 ConditionPathExists=|@SYSCONFDIR@/nvme/config.json
 ConditionPathExists=|@SYSCONFDIR@/nvme/discovery.conf
+Wants=modprobe@nvme_fabrics.service
+After=modprobe@nvme_fabrics.service
 After=network-online.target
 Before=remote-fs-pre.target
 
 [Service]
 Type=oneshot
-ExecStartPre=/sbin/modprobe nvme-fabrics
 ExecStart=@SBINDIR@/nvme connect-all --context=autoconnect
 
 [Install]