mirror of
https://github.com/systemd/systemd.git
synced 2025-01-21 22:04:01 +03:00
units: order service(s) before udevd, not udev-trigger (coldplug)
Since hotplugs happen as soon as udevd is started, there is not much sense in giving udev-trigger an After= dependency on any service. The device could be hotplugged before coldplug starts. This is intended to avoid the race window where we create the hwdb with the wrong selinux context (then fix it up afterwards). https://github.com/systemd/systemd/issues/3458#issuecomment-322444107
This commit is contained in:
parent
3533b49e74
commit
1d422b153b
@ -10,7 +10,7 @@ Description=udev Coldplug all Devices
|
||||
Documentation=man:udev(7) man:systemd-udevd.service(8)
|
||||
DefaultDependencies=no
|
||||
Wants=systemd-udevd.service
|
||||
After=systemd-udevd-kernel.socket systemd-udevd-control.socket systemd-hwdb-update.service
|
||||
After=systemd-udevd-kernel.socket systemd-udevd-control.socket
|
||||
Before=sysinit.target
|
||||
ConditionPathIsReadWrite=/sys
|
||||
|
||||
|
@ -9,7 +9,7 @@
|
||||
Description=udev Kernel Device Manager
|
||||
Documentation=man:systemd-udevd.service(8) man:udev(7)
|
||||
DefaultDependencies=no
|
||||
After=systemd-sysusers.service
|
||||
After=systemd-sysusers.service systemd-hwdb-update.service
|
||||
Before=sysinit.target
|
||||
ConditionPathIsReadWrite=/sys
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user