X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fudev.xml;h=0746618d005891dfd177636e63afc9d02509b2a9;hp=168b1dc1501e84c708041c394bc20eee81ceeb5c;hb=b1239c3fb3d19ff7273a8e5ead5c42f055d10b92;hpb=d3a2386d15d73b34fa990960696f87e0503ffdb2 diff --git a/man/udev.xml b/man/udev.xml index 168b1dc15..0746618d0 100644 --- a/man/udev.xml +++ b/man/udev.xml @@ -41,7 +41,7 @@ names provide a way to reliably identify devices based on their properties or current configuration. - The udev daemon, udevd + The udev daemon, systemd-udevd.service 8, receives device uevents directly from the kernel whenever a device is added or removed from the system, or it changes its state. When udev receives a device event, it matches its configured set of rules @@ -64,14 +64,6 @@ It consists of a set of variables allowing the user to override default udev values. The following variables can be set: - - - - Specifies where to place the device nodes in the filesystem. - The default value is /dev. - - - @@ -287,6 +279,8 @@ successfully. The device properties are made available to the executed program in the environment. The program's stdout is available in the RESULT key. + This can only be used for very short-running foreground tasks. For details + see . @@ -341,15 +335,20 @@ The name of a symlink targeting the node. Every matching rule adds - this value to the list of symlinks to be created. Multiple symlinks may be - specified by separating the names by the space character. In case multiple - devices claim the same name, the link always points to the device with - the highest link_priority. If the current device goes away, the links are - re-evaluated and the device with the next highest link_priority becomes the owner of - the link. If no link_priority is specified, the order of the devices (and - which one of them owns the link) is undefined. Also, symlink names must - never conflict with the kernel's default device node names, as that would - result in unpredictable behavior. + this value to the list of symlinks to be created. + The set of characters to name a symlink is limited. Allowed + characters are [0-9A-Za-z#+-.:=@_/], valid utf8 character sequences, + and "\x00" hex encoding. All other characters are replaced by + a '_' character. + Multiple symlinks may be specified by separating the names by the + space character. In case multiple devices claim the same name, the link + always points to the device with the highest link_priority. If the current + device goes away, the links are re-evaluated and the device with the + next highest link_priority becomes the owner of the link. If no + link_priority is specified, the order of the devices (and which one of + them owns the link) is undefined. + Symlink names must never conflict with the kernel's default device + node names, as that would result in unpredictable behavior. @@ -401,10 +400,12 @@ /usr/lib/udev, otherwise the absolute path must be specified. The program name and following arguments are separated by spaces. Single quotes can be used to specify arguments with spaces. - This can only be used for very short running tasks. Running an + This can only be used for very short-running foreground tasks. Running an event process for a long period of time may block all further events for - this or a dependent device. Starting daemons or other long running processes - is not appropriate for udev. + this or a dependent device. + Starting daemons or other long running processes is not appropriate + for udev; the forked processes, detached or not, will be unconditionally + killed after the event handling has finished. @@ -470,6 +471,8 @@ + This can only be used for very short-running foreground tasks. For details + see . @@ -513,10 +516,9 @@ Apply the permissions specified in this rule to the static device node with - the specified name. Static device nodes might be provided by kernel modules - or copied from /usr/lib/udev/devices. These nodes might not have - a corresponding kernel device at the time udevd is started; they can trigger - automatic kernel module loading. + the specified name. Static device node creation can be requested by kernel modules. + These nodes might not have a corresponding kernel device at the time systemd-udevd is + started; they can trigger automatic kernel module loading. @@ -694,7 +696,7 @@ See Also - udevd8 + systemd-udevd.service8 , udevadm8