From: Yu Watanabe Date: Wed, 26 Oct 2022 05:00:47 +0000 (+0900) Subject: unit: also prioritize input devices when triggering devices X-Git-Tag: v252~29 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=403ca5b8b4e5092639d350f84994b4cfb357e1aa;p=thirdparty%2Fsystemd.git unit: also prioritize input devices when triggering devices As in most cases, tty device without input devices is meaningless. This also swaps the priority of tty and net: - input devices are often connected under USB bus, hence may take slightly much time to be initialized. As, described in the above, in most cases it is allowed that tty devices are initialized just before input devices, - network configuration usually requires much time, e.g. DHCP or RA, hence it is better that network interfaces initialized. Then, network services can start DHCP client or friends earlier. Fixes #24026. --- diff --git a/units/systemd-udev-trigger.service b/units/systemd-udev-trigger.service index 0175a148584..cb1e4f9fea5 100644 --- a/units/systemd-udev-trigger.service +++ b/units/systemd-udev-trigger.service @@ -19,4 +19,4 @@ ConditionPathIsReadWrite=/sys [Service] Type=oneshot RemainAfterExit=yes -ExecStart=-udevadm trigger --type=all --action=add --prioritized-subsystem=module,block,tpmrm,tty,net +ExecStart=-udevadm trigger --type=all --action=add --prioritized-subsystem=module,block,tpmrm,net,tty,input