From f27bb6abd3b825034e0dde631ae3047128d2162d Mon Sep 17 00:00:00 2001 From: Dimitri John Ledkov Date: Fri, 13 Dec 2019 23:22:51 +0000 Subject: [PATCH] initrd: make udev cleanup service confict trigger and settle too Otherwise, systemd-udev-trigger|settle.service that ran in the initrd may ramain active, and never re-run again from the system root. This is observed by forexample examining ESP with udevadm info, which in the initrd has all the ID_* variables, and none of them in fully booted system. --- units/initrd-udevadm-cleanup-db.service.in | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/units/initrd-udevadm-cleanup-db.service.in b/units/initrd-udevadm-cleanup-db.service.in index 5059605c27b..09af690986c 100644 --- a/units/initrd-udevadm-cleanup-db.service.in +++ b/units/initrd-udevadm-cleanup-db.service.in @@ -11,8 +11,8 @@ Description=Cleanup udevd DB DefaultDependencies=no ConditionPathExists=/etc/initrd-release -Conflicts=systemd-udevd.service systemd-udevd-control.socket systemd-udevd-kernel.socket -After=systemd-udevd.service systemd-udevd-control.socket systemd-udevd-kernel.socket +Conflicts=systemd-udevd.service systemd-udevd-control.socket systemd-udevd-kernel.socket systemd-udev-trigger.service systemd-udev-settle.service +After=systemd-udevd.service systemd-udevd-control.socket systemd-udevd-kernel.socket systemd-udev-trigger.service systemd-udev-settle.service Before=initrd-switch-root.target [Service] -- 2.47.3