]>
Commit | Line | Data |
---|---|---|
1 | .TH UDEVD 8 "February 2004" "" "Linux Administrator's Manual" | |
2 | .SH NAME | |
3 | udevd, udevdsend \- udev event serializer daemon and udev event sender | |
4 | .SH SYNOPSIS | |
5 | .BI udevsend | |
6 | .SH "DESCRIPTION" | |
7 | .B udevd | |
8 | allows the serialization of | |
9 | .BR hotplug (8) | |
10 | events. The events generated by the kernel may arrive in random order | |
11 | in userspace, that makes it neccessary to reorder them. | |
12 | .br | |
13 | .B udevd | |
14 | takes care of the kernel supplied | |
15 | .B SEQNUM | |
16 | sequence number and arranges the events for execution in the correct order. | |
17 | Missing sequences delay the execution of the following events until a timeout | |
18 | is reached. Events without any sequence number are bypassing the queue and | |
19 | will be executed immediately. | |
20 | .br | |
21 | For each event a | |
22 | .BR udev (8) | |
23 | instance is executed in the background with the complete environment received | |
24 | by the hotplug event. All further events for the same device are delayed until | |
25 | the execution is finished. This way there will never be more than one instance | |
26 | running for a single device at the same time. | |
27 | .br | |
28 | .B udevd | |
29 | receives the events from | |
30 | .B udevsend | |
31 | If | |
32 | .B udevd | |
33 | isn't already running, | |
34 | .B udevsend | |
35 | will start it. | |
36 | .SH "SEE ALSO" | |
37 | .BR udev (8), | |
38 | .BR udevinfo (8), | |
39 | .BR hotplug (8) | |
40 | .SH AUTHORS | |
41 | .B udevd | |
42 | was developed primarily by Kay Sievers <kay.sievers@vrfy.org>, with much help | |
43 | from others. |