mirrors/systemd
0
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-11-26 19:53:45 +08:00
Code Issues Packages Projects Releases Wiki Activity
main
systemd/units/systemd-udev-trigger.service

23 lines
758 B
SYSTEMD
Raw Permalink Normal View History

license: LGPL-2.1+ -> LGPL-2.1-or-later
2020-11-09 12:23:58 +08:00
# SPDX-License-Identifier: LGPL-2.1-or-later
Add SPDX license headers to unit files
2017-11-19 00:35:03 +08:00
#
units: introduce new Documentation= field and make use of it everywhere This should help making the boot process a bit easier to explore and understand for the administrator. The simple idea is that "systemctl status" now shows a link to documentation alongside the other status and decriptionary information of a service. This patch adds the necessary fields to all our shipped units if we have proper documentation for them.
2012-05-21 21:12:18 +08:00
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
systemd: bind udev control socket in systemd and split udev.service We should bind the udev socket from systemd, so we are sure that the abstract namespace socket is always bound by a root process and there is never a window during an update where an untrusted process can steal our socket. Also split the udev.service file, so that the daemon can be updated/restarted without triggering any coldplug events.
2011-03-23 23:40:23 +08:00
[Unit]
units: tweak udev unit descriptions
2020-06-02 21:36:17 +08:00
Description=Coldplug All udev Devices
man: refer to udevd by its service name not binary name Since the binary name is now hidden away in /usr/lib/ the primary user handle for the udev service is the unit name, hence change the man page to be available under the unit name, and make the binary name an alias for it.
2012-06-22 16:38:40 +08:00
Documentation=man:udev(7) man:systemd-udevd.service(8)
units: order all udev services before sysinit.target, too Not that it would matter much, but let's make things a bit more systematic: early boot services shall order themselves before sysinit.target, and nothing else.
2013-03-26 04:22:52 +08:00
DefaultDependencies=no
units: Rename systemd-udev.service to systemd-udevd.service This naming convention is more inline with other systemd daemon unit names (systemd-logind.service, systemd-localed.service etc) The companion .socket units have also been renamed, however the -trigger and -settle units keep their current name as these are not directly related to daemon process itself.
2012-07-03 03:35:14 +08:00
Wants=systemd-udevd.service
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
2017-08-15 21:22:44 +08:00
After=systemd-udevd-kernel.socket systemd-udevd-control.socket
units: order all udev services before sysinit.target, too Not that it would matter much, but let's make things a bit more systematic: early boot services shall order themselves before sysinit.target, and nothing else.
2013-03-26 04:22:52 +08:00
Before=sysinit.target
udev: replace CAP_MKNOD by writable /sys condition
2013-08-18 01:07:42 +08:00
ConditionPathIsReadWrite=/sys
systemd: bind udev control socket in systemd and split udev.service We should bind the udev socket from systemd, so we are sure that the abstract namespace socket is always bound by a root process and there is never a window during an update where an untrusted process can steal our socket. Also split the udev.service file, so that the daemon can be updated/restarted without triggering any coldplug events.
2011-03-23 23:40:23 +08:00
[Service]
Type=oneshot
RemainAfterExit=yes
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.
2022-10-26 13:00:47 +08:00
ExecStart=-udevadm trigger --type=all --action=add --prioritized-subsystem=module,block,tpmrm,net,tty,input
Reference in New Issue Copy Permalink