Debian Codegraph @

upstream/debian-unstable/man8/systemd-udev-settle.service.8

raw
1 '\" t
2 .TH "SYSTEMD\-UDEV\-SETTLE\&.SERVICE" "8" "" "systemd 261~rc3" "systemd-udev-settle.service"
3 .\" -----------------------------------------------------------------
4 .\" * Define some portability stuff
5 .\" -----------------------------------------------------------------
6 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
7 .\" http://bugs.debian.org/507673
8 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
9 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
10 .ie \n(.g .ds Aq \(aq
11 .el .ds Aq '
12 .\" -----------------------------------------------------------------
13 .\" * set default formatting
14 .\" -----------------------------------------------------------------
15 .\" disable hyphenation
16 .nh
17 .\" disable justification (adjust text to left margin only)
18 .ad l
19 .\" -----------------------------------------------------------------
20 .\" * MAIN CONTENT STARTS HERE *
21 .\" -----------------------------------------------------------------
22 .SH "NAME"
23 systemd-udev-settle.service \- Wait for all pending udev events to be handled
24 .SH "SYNOPSIS"
25 .PP
26 systemd\-udev\-settle\&.service
27 .SH "DESCRIPTION"
28 .PP
29 This service calls
30 \fBudevadm settle\fR
31 to wait until all events that have been queued by
32 \fBudev\fR(7)
33 have been processed\&. It is a crude way to wait until "all" hardware has been discovered\&. Services may pull in this service and order themselves after it to wait for the udev queue to be empty\&.
34 .PP
35 \fIUsing this service is not recommended\&.\fR
36 There can be no guarantee that hardware is fully discovered at any specific time, because the kernel does hardware detection asynchronously, and certain buses and devices take a very long time to become ready, and also additional hardware may be plugged in at any time\&. Instead, services should subscribe to udev events and react to any new hardware as it is discovered\&. Services that, based on configuration, expect certain devices to appear, may warn or report failure after a timeout\&. This timeout should be tailored to the hardware type\&. Waiting for
37 systemd\-udev\-settle\&.service
38 usually slows boot significantly, because it means waiting for all unrelated events too\&.
39 .SH "SEE ALSO"
40 .PP
41 \fBudev\fR(7), \fBudevadm\fR(8)