From: Tom Gundersen Date: Mon, 18 Mar 2013 14:58:37 +0000 (+0100) Subject: man: udev - move documentation of configuration file X-Git-Tag: v199~173 X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=commitdiff_plain;h=6ec0ac43bb1f9f8b8b435ba6e5d55dc7cc84c3c6;hp=61e536e1b7f3a7448428a05bafe1ea64d7e51938;ds=sidebyside man: udev - move documentation of configuration file Moved from udev(7) to systemd-udevd.service(8), where the rest of the documentation of the configuration of the daemon lives. --- diff --git a/man/systemd-udevd.service.xml b/man/systemd-udevd.service.xml index 2b9a29adc..35e254384 100644 --- a/man/systemd-udevd.service.xml +++ b/man/systemd-udevd.service.xml @@ -157,6 +157,23 @@ + Configuration file + udev expects its main configuration file at /etc/udev/udev.conf. + It consists of a set of variables allowing the user to override default udev values. All + empty lines or lines beginning with '#' are ignored. The following variables can be + set: + + + udev_log + + The logging priority. Valid values are the numerical syslog priorities + or their textual representations: , + and . + + + + + See Also diff --git a/man/udev.xml b/man/udev.xml index 34b1e6fd6..eab525f0f 100644 --- a/man/udev.xml +++ b/man/udev.xml @@ -54,28 +54,7 @@ sources is provided by the library libudev. - Configuration - udev configuration files are placed in /etc/udev - and /usr/lib/udev. All empty lines or lines beginning with - '#' are ignored. - - Configuration file - udev expects its main configuration file at /etc/udev/udev.conf. - It consists of a set of variables allowing the user to override default udev values. - The following variables can be set: - - - udev_log - - The logging priority. Valid values are the numerical syslog priorities - or their textual representations: , - and . - - - - - - Rules files + Rules files The udev rules are read from the files located in the system rules directory /usr/lib/udev/rules.d, the volatile runtime directory /run/udev/rules.d @@ -94,9 +73,10 @@ extensions are ignored. Every line in the rules file contains at least one key-value pair. + Except for empty lines or lines beginning with '#', which are ignored. There are two kinds of keys: match and assignment. - If all match keys are matching against its value, the rule gets applied and the - assignment keys get the specified value assigned. + If all match keys match against their values, the rule gets applied and the + assignment keys get the specified values assigned. A matching rule may rename a network interface, add symlinks pointing to the device node, or run a specified program as part of @@ -714,7 +694,6 @@ -