From 25307eee7fb70d3931ebad2a3a0c951a2bf10d26 Mon Sep 17 00:00:00 2001 From: Lars Wendler Date: Mon, 27 Dec 2021 00:53:21 +0100 Subject: [PATCH] Don't use systemd-run in 69-dm-lvm.rules some people don't run systemd --- udev/69-dm-lvm.rules.in | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/udev/69-dm-lvm.rules.in b/udev/69-dm-lvm.rules.in index ff1568145..34b669315 100644 --- a/udev/69-dm-lvm.rules.in +++ b/udev/69-dm-lvm.rules.in @@ -58,8 +58,8 @@ LABEL="lvm_scan" # LVM_VG_NAME_COMPLETE='foo' # # When the VG is complete it can be activated, so -# vgchange -aay is run. It is run via -# systemd since it can take longer to run than +# vgchange -aay is run. It can take +# longer to run than # udev wants to block when processing rules. # (if there are hundreds of LVs to activate, # the vgchange can take many seconds.) @@ -76,7 +76,7 @@ LABEL="lvm_scan" # it's better suited to appearing in the journal. IMPORT{program}="(LVM_EXEC)/lvm pvscan --cache --listvg --checkcomplete --vgonline --autoactivation event --udevoutput --journal=output $env{DEVNAME}" -ENV{LVM_VG_NAME_COMPLETE}=="?*", RUN+="(SYSTEMDRUN) --no-block --property DefaultDependencies=no --unit lvm-activate-$env{LVM_VG_NAME_COMPLETE} (LVM_EXEC)/lvm vgchange -aay --autoactivation event $env{LVM_VG_NAME_COMPLETE}" +ENV{LVM_VG_NAME_COMPLETE}=="?*", RUN+="(LVM_EXEC)/lvm vgchange -aay --autoactivation event $env{LVM_VG_NAME_COMPLETE}" GOTO="lvm_end" LABEL="lvm_end" -- 2.39.2