By providing the execution context from the systemd service files,
nvme-cli can figure out if it is noop when looking at the configuration
files.
Signed-off-by: Daniel Wagner <dwagner@suse.de>
[Service]
Type=oneshot
ExecStartPre=/sbin/modprobe nvme-fabrics
-ExecStart=@SBINDIR@/nvme connect-all
+ExecStart=@SBINDIR@/nvme connect-all --context=autoconnect
[Install]
WantedBy=default.target
[Service]
Type=simple
Environment="CONNECT_ARGS=%i"
-ExecStart=/bin/sh -c "@SBINDIR@/nvme connect-all --quiet `/bin/echo -e '${CONNECT_ARGS}'`"
+ExecStart=/bin/sh -c "@SBINDIR@/nvme connect-all --context=autoconnect --quiet `/bin/echo -e '${CONNECT_ARGS}'`"