2018-07-02 21:15:39 +00:00
|
|
|
<?xml version='1.0'?>
|
2019-03-14 13:40:58 +00:00
|
|
|
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
2023-12-25 14:48:33 +00:00
|
|
|
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
|
2020-11-09 04:23:58 +00:00
|
|
|
<!-- SPDX-License-Identifier: LGPL-2.1-or-later -->
|
2017-11-18 16:52:56 +00:00
|
|
|
|
2014-02-13 19:33:51 +00:00
|
|
|
<refentry id="systemd-udevd.service"
|
|
|
|
xmlns:xi="http://www.w3.org/2001/XInclude">
|
|
|
|
|
2010-05-24 15:00:15 +00:00
|
|
|
<refentryinfo>
|
2012-06-25 22:12:00 +00:00
|
|
|
<title>systemd-udevd.service</title>
|
2012-04-04 12:42:32 +00:00
|
|
|
<productname>systemd</productname>
|
2010-05-24 15:00:15 +00:00
|
|
|
</refentryinfo>
|
2005-08-30 02:41:42 +00:00
|
|
|
|
2010-05-24 15:00:15 +00:00
|
|
|
<refmeta>
|
2012-07-29 09:58:41 +00:00
|
|
|
<refentrytitle>systemd-udevd.service</refentrytitle>
|
2010-05-24 15:00:15 +00:00
|
|
|
<manvolnum>8</manvolnum>
|
|
|
|
</refmeta>
|
2005-08-30 02:41:42 +00:00
|
|
|
|
2010-05-24 15:00:15 +00:00
|
|
|
<refnamediv>
|
2012-07-02 19:35:14 +00:00
|
|
|
<refname>systemd-udevd.service</refname>
|
|
|
|
<refname>systemd-udevd-control.socket</refname>
|
|
|
|
<refname>systemd-udevd-kernel.socket</refname>
|
2012-07-29 09:58:41 +00:00
|
|
|
<refname>systemd-udevd</refname>
|
2012-06-22 08:38:40 +00:00
|
|
|
<refpurpose>Device event managing daemon</refpurpose>
|
2010-05-24 15:00:15 +00:00
|
|
|
</refnamediv>
|
2005-08-30 02:41:42 +00:00
|
|
|
|
2010-05-24 15:00:15 +00:00
|
|
|
<refsynopsisdiv>
|
2012-07-02 19:35:14 +00:00
|
|
|
<para><filename>systemd-udevd.service</filename></para>
|
|
|
|
<para><filename>systemd-udevd-control.socket</filename></para>
|
|
|
|
<para><filename>systemd-udevd-kernel.socket</filename></para>
|
2012-06-22 08:38:40 +00:00
|
|
|
|
2010-05-24 15:00:15 +00:00
|
|
|
<cmdsynopsis>
|
2015-06-18 17:47:44 +00:00
|
|
|
<command>/usr/lib/systemd/systemd-udevd</command>
|
2010-05-24 15:00:15 +00:00
|
|
|
<arg><option>--daemon</option></arg>
|
|
|
|
<arg><option>--debug</option></arg>
|
2010-05-28 13:11:36 +00:00
|
|
|
<arg><option>--children-max=</option></arg>
|
|
|
|
<arg><option>--exec-delay=</option></arg>
|
2014-07-29 07:06:14 +00:00
|
|
|
<arg><option>--event-timeout=</option></arg>
|
2010-05-24 15:00:15 +00:00
|
|
|
<arg><option>--resolve-names=early|late|never</option></arg>
|
2010-05-28 13:11:36 +00:00
|
|
|
<arg><option>--version</option></arg>
|
2010-05-24 15:00:15 +00:00
|
|
|
<arg><option>--help</option></arg>
|
|
|
|
</cmdsynopsis>
|
2012-06-22 08:38:40 +00:00
|
|
|
|
2010-05-24 15:00:15 +00:00
|
|
|
</refsynopsisdiv>
|
2005-08-30 02:41:42 +00:00
|
|
|
|
2010-05-24 15:00:15 +00:00
|
|
|
<refsect1><title>Description</title>
|
2012-07-28 21:10:15 +00:00
|
|
|
<para><command>systemd-udevd</command> listens to kernel uevents.
|
2014-07-31 08:01:19 +00:00
|
|
|
For every event, systemd-udevd executes matching instructions
|
|
|
|
specified in udev rules. See <citerefentry>
|
|
|
|
<refentrytitle>udev</refentrytitle><manvolnum>7</manvolnum>
|
|
|
|
</citerefentry>.</para>
|
|
|
|
|
2014-10-23 04:12:50 +00:00
|
|
|
<para>The behavior of the daemon can be configured using
|
|
|
|
<citerefentry><refentrytitle>udev.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
|
2014-11-06 19:06:30 +00:00
|
|
|
its command line options, environment variables, and on the kernel
|
|
|
|
command line, or changed dynamically with <command>udevadm
|
2014-10-23 04:12:50 +00:00
|
|
|
control</command>.
|
2014-07-31 08:01:19 +00:00
|
|
|
</para>
|
2010-05-24 15:00:15 +00:00
|
|
|
</refsect1>
|
2005-08-30 02:41:42 +00:00
|
|
|
|
2010-05-24 15:00:15 +00:00
|
|
|
<refsect1><title>Options</title>
|
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
2017-12-04 04:33:46 +00:00
|
|
|
<term><option>-d</option></term>
|
2010-05-24 15:00:15 +00:00
|
|
|
<term><option>--daemon</option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>Detach and run in the background.</para>
|
2023-09-18 15:03:38 +00:00
|
|
|
|
|
|
|
<xi:include href="version-info.xml" xpointer="v186"/>
|
2010-05-24 15:00:15 +00:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2014-02-13 19:33:51 +00:00
|
|
|
|
2010-05-24 15:00:15 +00:00
|
|
|
<varlistentry>
|
2017-12-04 04:33:46 +00:00
|
|
|
<term><option>-D</option></term>
|
2010-05-28 13:11:36 +00:00
|
|
|
<term><option>--debug</option></term>
|
|
|
|
<listitem>
|
2014-02-15 03:00:06 +00:00
|
|
|
<para>Print debug messages to standard error.</para>
|
2023-09-18 15:03:38 +00:00
|
|
|
|
|
|
|
<xi:include href="version-info.xml" xpointer="v186"/>
|
2010-05-28 13:11:36 +00:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2014-02-13 19:33:51 +00:00
|
|
|
|
2010-05-28 13:11:36 +00:00
|
|
|
<varlistentry>
|
2020-06-05 13:42:45 +00:00
|
|
|
<term><option>-c</option></term>
|
2010-05-28 13:11:36 +00:00
|
|
|
<term><option>--children-max=</option></term>
|
2010-05-24 15:00:15 +00:00
|
|
|
<listitem>
|
2012-07-28 21:10:15 +00:00
|
|
|
<para>Limit the number of events executed in parallel.</para>
|
2023-09-18 15:03:38 +00:00
|
|
|
|
|
|
|
<xi:include href="version-info.xml" xpointer="v186"/>
|
2010-05-24 15:00:15 +00:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2014-02-13 19:33:51 +00:00
|
|
|
|
2010-05-24 15:00:15 +00:00
|
|
|
<varlistentry>
|
2020-06-05 13:42:45 +00:00
|
|
|
<term><option>-e</option></term>
|
2010-05-28 13:11:36 +00:00
|
|
|
<term><option>--exec-delay=</option></term>
|
2010-05-24 15:00:15 +00:00
|
|
|
<listitem>
|
2021-04-12 08:09:47 +00:00
|
|
|
<para>Delay the execution of each <varname>RUN{<replaceable>program</replaceable>}</varname>
|
|
|
|
parameter by the given number of seconds. This option
|
2014-02-15 03:00:06 +00:00
|
|
|
might be useful when debugging system crashes during
|
|
|
|
coldplug caused by loading non-working kernel
|
|
|
|
modules.</para>
|
2023-09-18 15:03:38 +00:00
|
|
|
|
|
|
|
<xi:include href="version-info.xml" xpointer="v186"/>
|
2010-05-24 15:00:15 +00:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2014-02-13 19:33:51 +00:00
|
|
|
|
2014-07-29 07:06:14 +00:00
|
|
|
<varlistentry>
|
2020-06-05 13:42:45 +00:00
|
|
|
<term><option>-t</option></term>
|
2014-07-29 07:06:14 +00:00
|
|
|
<term><option>--event-timeout=</option></term>
|
|
|
|
<listitem>
|
2014-07-29 13:18:27 +00:00
|
|
|
<para>Set the number of seconds to wait for events to finish. After
|
2014-08-03 05:11:12 +00:00
|
|
|
this time, the event will be terminated. The default is 180 seconds.</para>
|
2023-09-18 15:03:38 +00:00
|
|
|
|
|
|
|
<xi:include href="version-info.xml" xpointer="v216"/>
|
2014-07-29 07:06:14 +00:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2020-04-09 09:14:25 +00:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>-s</option></term>
|
|
|
|
<term><option>--timeout-signal=</option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>Set the signal which <filename>systemd-udevd</filename> will send to
|
2020-06-26 19:30:04 +00:00
|
|
|
forked off processes after reaching event timeout. The setting can be overridden
|
2020-04-09 09:14:25 +00:00
|
|
|
at boot time with the kernel command line option
|
|
|
|
<varname>udev.timeout_signal=</varname>. Setting to <constant>SIGABRT</constant>
|
|
|
|
may be helpful in order to debug worker timeouts. Defaults to
|
|
|
|
<constant>SIGKILL</constant>. Note that setting the option on the command line
|
|
|
|
overrides the setting from the configuration file.
|
|
|
|
</para>
|
2023-08-22 16:52:36 +00:00
|
|
|
|
|
|
|
<xi:include href="version-info.xml" xpointer="v246"/>
|
2020-04-09 09:14:25 +00:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2010-05-24 15:00:15 +00:00
|
|
|
<varlistentry>
|
2020-06-05 13:42:45 +00:00
|
|
|
<term><option>-N</option></term>
|
2010-05-28 13:11:36 +00:00
|
|
|
<term><option>--resolve-names=</option></term>
|
2010-05-24 15:00:15 +00:00
|
|
|
<listitem>
|
2012-04-16 21:32:22 +00:00
|
|
|
<para>Specify when systemd-udevd should resolve names of users and groups.
|
2014-02-17 02:37:13 +00:00
|
|
|
When set to <option>early</option> (the default), names will be
|
2010-05-24 15:00:15 +00:00
|
|
|
resolved when the rules are parsed. When set to
|
2014-02-17 02:37:13 +00:00
|
|
|
<option>late</option>, names will be resolved for every event.
|
|
|
|
When set to <option>never</option>, names will never be resolved
|
2010-05-24 15:00:15 +00:00
|
|
|
and all devices will be owned by root.</para>
|
2023-09-18 15:03:38 +00:00
|
|
|
|
|
|
|
<xi:include href="version-info.xml" xpointer="v186"/>
|
2010-05-24 15:00:15 +00:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2014-02-13 19:33:51 +00:00
|
|
|
|
2017-12-04 04:33:46 +00:00
|
|
|
<xi:include href="standard-options.xml" xpointer="help" />
|
2014-02-13 19:33:51 +00:00
|
|
|
<xi:include href="standard-options.xml" xpointer="version" />
|
2010-05-24 15:00:15 +00:00
|
|
|
</variablelist>
|
|
|
|
</refsect1>
|
2005-08-30 02:41:42 +00:00
|
|
|
|
2010-05-29 20:23:48 +00:00
|
|
|
<refsect1><title>Kernel command line</title>
|
2013-01-26 15:47:16 +00:00
|
|
|
<variablelist class='kernel-commandline-options'>
|
2020-06-02 13:15:24 +00:00
|
|
|
<para>Parameters prefixed with "rd." will be read when <command>systemd-udevd</command> is used in an
|
|
|
|
initrd, those without will be processed both in the initrd and on the host.</para>
|
2010-05-29 20:23:48 +00:00
|
|
|
<varlistentry>
|
2020-09-21 09:10:50 +00:00
|
|
|
<term><varname>udev.log_level=</varname></term>
|
|
|
|
<term><varname>rd.udev.log_level=</varname></term>
|
2010-05-29 20:23:48 +00:00
|
|
|
<listitem>
|
2014-11-01 18:33:01 +00:00
|
|
|
<para>Set the log level.</para>
|
2023-08-22 16:52:36 +00:00
|
|
|
|
|
|
|
<xi:include href="version-info.xml" xpointer="v247"/>
|
2010-05-29 20:23:48 +00:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
util-lib: various improvements to kernel command line parsing
This improves kernel command line parsing in a number of ways:
a) An kernel option "foo_bar=xyz" is now considered equivalent to
"foo-bar-xyz", i.e. when comparing kernel command line option names "-" and
"_" are now considered equivalent (this only applies to the option names
though, not the option values!). Most of our kernel options used "-" as word
separator in kernel command line options so far, but some used "_". With
this change, which was a source of confusion for users (well, at least of
one user: myself, I just couldn't remember that it's systemd.debug-shell,
not systemd.debug_shell). Considering both as equivalent is inspired how
modern kernel module loading normalizes all kernel module names to use
underscores now too.
b) All options previously using a dash for separating words in kernel command
line options now use an underscore instead, in all documentation and in
code. Since a) has been implemented this should not create any compatibility
problems, but normalizes our documentation and our code.
c) All kernel command line options which take booleans (or are boolean-like)
have been reworked so that "foobar" (without argument) is now equivalent to
"foobar=1" (but not "foobar=0"), thus normalizing the handling of our
boolean arguments. Specifically this means systemd.debug-shell and
systemd_debug_shell=1 are now entirely equivalent.
d) All kernel command line options which take an argument, and where no
argument is specified will now result in a log message. e.g. passing just
"systemd.unit" will no result in a complain that it needs an argument. This
is implemented in the proc_cmdline_missing_value() function.
e) There's now a call proc_cmdline_get_bool() similar to proc_cmdline_get_key()
that parses booleans (following the logic explained in c).
f) The proc_cmdline_parse() call's boolean argument has been replaced by a new
flags argument that takes a common set of bits with proc_cmdline_get_key().
g) All kernel command line APIs now begin with the same "proc_cmdline_" prefix.
h) There are now tests for much of this. Yay!
2016-12-12 17:29:15 +00:00
|
|
|
<term><varname>udev.children_max=</varname></term>
|
|
|
|
<term><varname>rd.udev.children_max=</varname></term>
|
2010-05-29 20:23:48 +00:00
|
|
|
<listitem>
|
2012-07-28 21:10:15 +00:00
|
|
|
<para>Limit the number of events executed in parallel.</para>
|
2023-08-22 16:52:36 +00:00
|
|
|
|
2023-09-18 15:03:38 +00:00
|
|
|
<xi:include href="version-info.xml" xpointer="v186"/>
|
2010-05-29 20:23:48 +00:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
util-lib: various improvements to kernel command line parsing
This improves kernel command line parsing in a number of ways:
a) An kernel option "foo_bar=xyz" is now considered equivalent to
"foo-bar-xyz", i.e. when comparing kernel command line option names "-" and
"_" are now considered equivalent (this only applies to the option names
though, not the option values!). Most of our kernel options used "-" as word
separator in kernel command line options so far, but some used "_". With
this change, which was a source of confusion for users (well, at least of
one user: myself, I just couldn't remember that it's systemd.debug-shell,
not systemd.debug_shell). Considering both as equivalent is inspired how
modern kernel module loading normalizes all kernel module names to use
underscores now too.
b) All options previously using a dash for separating words in kernel command
line options now use an underscore instead, in all documentation and in
code. Since a) has been implemented this should not create any compatibility
problems, but normalizes our documentation and our code.
c) All kernel command line options which take booleans (or are boolean-like)
have been reworked so that "foobar" (without argument) is now equivalent to
"foobar=1" (but not "foobar=0"), thus normalizing the handling of our
boolean arguments. Specifically this means systemd.debug-shell and
systemd_debug_shell=1 are now entirely equivalent.
d) All kernel command line options which take an argument, and where no
argument is specified will now result in a log message. e.g. passing just
"systemd.unit" will no result in a complain that it needs an argument. This
is implemented in the proc_cmdline_missing_value() function.
e) There's now a call proc_cmdline_get_bool() similar to proc_cmdline_get_key()
that parses booleans (following the logic explained in c).
f) The proc_cmdline_parse() call's boolean argument has been replaced by a new
flags argument that takes a common set of bits with proc_cmdline_get_key().
g) All kernel command line APIs now begin with the same "proc_cmdline_" prefix.
h) There are now tests for much of this. Yay!
2016-12-12 17:29:15 +00:00
|
|
|
<term><varname>udev.exec_delay=</varname></term>
|
|
|
|
<term><varname>rd.udev.exec_delay=</varname></term>
|
2010-05-29 20:23:48 +00:00
|
|
|
<listitem>
|
2021-04-12 08:09:47 +00:00
|
|
|
<para>Delay the execution of each <varname>RUN{<replaceable>program</replaceable>}</varname> parameter by the given
|
2012-07-28 21:10:15 +00:00
|
|
|
number of seconds. This option might be useful when
|
|
|
|
debugging system crashes during coldplug caused by loading
|
|
|
|
non-working kernel modules.</para>
|
2023-08-22 16:52:36 +00:00
|
|
|
|
2023-09-18 15:03:38 +00:00
|
|
|
<xi:include href="version-info.xml" xpointer="v186"/>
|
2010-05-24 15:00:15 +00:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2014-07-29 07:06:14 +00:00
|
|
|
<varlistentry>
|
util-lib: various improvements to kernel command line parsing
This improves kernel command line parsing in a number of ways:
a) An kernel option "foo_bar=xyz" is now considered equivalent to
"foo-bar-xyz", i.e. when comparing kernel command line option names "-" and
"_" are now considered equivalent (this only applies to the option names
though, not the option values!). Most of our kernel options used "-" as word
separator in kernel command line options so far, but some used "_". With
this change, which was a source of confusion for users (well, at least of
one user: myself, I just couldn't remember that it's systemd.debug-shell,
not systemd.debug_shell). Considering both as equivalent is inspired how
modern kernel module loading normalizes all kernel module names to use
underscores now too.
b) All options previously using a dash for separating words in kernel command
line options now use an underscore instead, in all documentation and in
code. Since a) has been implemented this should not create any compatibility
problems, but normalizes our documentation and our code.
c) All kernel command line options which take booleans (or are boolean-like)
have been reworked so that "foobar" (without argument) is now equivalent to
"foobar=1" (but not "foobar=0"), thus normalizing the handling of our
boolean arguments. Specifically this means systemd.debug-shell and
systemd_debug_shell=1 are now entirely equivalent.
d) All kernel command line options which take an argument, and where no
argument is specified will now result in a log message. e.g. passing just
"systemd.unit" will no result in a complain that it needs an argument. This
is implemented in the proc_cmdline_missing_value() function.
e) There's now a call proc_cmdline_get_bool() similar to proc_cmdline_get_key()
that parses booleans (following the logic explained in c).
f) The proc_cmdline_parse() call's boolean argument has been replaced by a new
flags argument that takes a common set of bits with proc_cmdline_get_key().
g) All kernel command line APIs now begin with the same "proc_cmdline_" prefix.
h) There are now tests for much of this. Yay!
2016-12-12 17:29:15 +00:00
|
|
|
<term><varname>udev.event_timeout=</varname></term>
|
|
|
|
<term><varname>rd.udev.event_timeout=</varname></term>
|
2014-07-29 07:06:14 +00:00
|
|
|
<listitem>
|
|
|
|
<para>Wait for events to finish up to the given number
|
|
|
|
of seconds. This option might be useful if events are
|
2014-07-29 13:18:27 +00:00
|
|
|
terminated due to kernel drivers taking too long to initialize.</para>
|
2023-08-22 16:52:36 +00:00
|
|
|
|
2023-09-18 15:03:38 +00:00
|
|
|
<xi:include href="version-info.xml" xpointer="v216"/>
|
2014-07-29 07:06:14 +00:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2020-04-09 09:14:25 +00:00
|
|
|
<varlistentry>
|
|
|
|
<term><varname>udev.timeout_signal=</varname></term>
|
|
|
|
<term><varname>rd.udev.timeout_signal=</varname></term>
|
|
|
|
<listitem>
|
|
|
|
<para>Specifies a signal that <filename>systemd-udevd</filename> will send to
|
|
|
|
workers on timeout. Note that kernel command line option overrides both the
|
|
|
|
setting in the configuration file and the one on the program command line.</para>
|
2023-08-22 16:52:36 +00:00
|
|
|
|
|
|
|
<xi:include href="version-info.xml" xpointer="v246"/>
|
2020-04-09 09:14:25 +00:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2020-06-02 13:15:24 +00:00
|
|
|
<varlistentry>
|
|
|
|
<term><varname>udev.blockdev_read_only</varname></term>
|
|
|
|
<term><varname>rd.udev.blockdev_read_only</varname></term>
|
|
|
|
<listitem>
|
|
|
|
<para>If specified, mark all physical block devices read-only as they appear. Synthetic block
|
|
|
|
devices (such as loopback block devices or device mapper devices) are left as they are. This is
|
|
|
|
useful to guarantee that the contents of physical block devices remains unmodified during runtime,
|
|
|
|
for example to implement fully stateless systems, for testing or for recovery situations where
|
|
|
|
corrupted file systems shall not be corrupted further through accidental modification.</para>
|
|
|
|
|
|
|
|
<para>A block device may be marked writable again by issuing the <command>blockdev
|
|
|
|
--setrw</command> command, see <citerefentry
|
|
|
|
project='man-pages'><refentrytitle>blockdev</refentrytitle><manvolnum>8</manvolnum></citerefentry>
|
|
|
|
for details.</para>
|
2023-08-22 16:52:36 +00:00
|
|
|
|
|
|
|
<xi:include href="version-info.xml" xpointer="v246"/>
|
2020-06-02 13:15:24 +00:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2013-03-17 04:23:33 +00:00
|
|
|
<varlistentry>
|
2013-03-18 18:31:34 +00:00
|
|
|
<term><varname>net.ifnames=</varname></term>
|
2013-03-17 04:23:33 +00:00
|
|
|
<listitem>
|
2013-03-18 18:31:34 +00:00
|
|
|
<para>Network interfaces are renamed to give them predictable names
|
2014-02-14 01:25:23 +00:00
|
|
|
when possible. It is enabled by default; specifying 0 disables it.</para>
|
2023-08-22 16:52:36 +00:00
|
|
|
|
|
|
|
<xi:include href="version-info.xml" xpointer="v199"/>
|
2013-03-17 04:23:33 +00:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2018-12-10 16:10:19 +00:00
|
|
|
<varlistentry>
|
2024-02-28 14:31:27 +00:00
|
|
|
<term><varname>net.naming_scheme=</varname></term>
|
2018-12-10 16:10:19 +00:00
|
|
|
<listitem>
|
|
|
|
<para>Network interfaces are renamed to give them predictable names when possible (unless
|
2019-05-09 10:34:30 +00:00
|
|
|
<varname>net.ifnames=0</varname> is specified, see above). With this kernel command line option it
|
|
|
|
is possible to pick a specific version of this algorithm and override the default chosen at
|
|
|
|
compilation time. Expects one of the naming scheme identifiers listed in
|
|
|
|
<citerefentry><refentrytitle>systemd.net-naming-scheme</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
|
|
|
|
or <literal>latest</literal> to select the latest scheme known (to this particular version of
|
|
|
|
<filename>systemd-udevd.service</filename>).</para>
|
meson: make net.naming-scheme= default configurable
This is useful for distributions, where the stability of interface names should
be preseved after an upgrade of systemd. So when some specific release of the
distro is made available, systemd defaults to the latest & greatest naming
scheme, and subsequent updates set the same default. This default may still
be overriden through the kernel and env var options.
A special value "latest" is also allowed. Without a specific name, it is harder
to verride from meson. In case of 'combo' options, meson reads the default
during the initial configuration, and "remembers" this choice. When systemd is
updated, old build/ directories could keep the old default, which would be
annoying. Hence, "latest" is introduced to make it explicit, yet follow the
upstream. This is actually useful for the user too, because it may be used
as an override, without having to actually specify a version.
2018-12-11 22:28:29 +00:00
|
|
|
|
|
|
|
<para>Note that selecting a specific scheme is not sufficient to fully stabilize interface naming:
|
|
|
|
the naming is generally derived from driver attributes exposed by the kernel. As the kernel is
|
|
|
|
updated, previously missing attributes <filename>systemd-udevd.service</filename> is checking might
|
|
|
|
appear, which affects older name derivation algorithms, too.</para>
|
2023-08-22 16:52:36 +00:00
|
|
|
|
|
|
|
<xi:include href="version-info.xml" xpointer="v240"/>
|
2018-12-10 16:10:19 +00:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2021-12-14 02:29:08 +00:00
|
|
|
<varlistentry>
|
2024-02-28 14:31:27 +00:00
|
|
|
<term><varname>net.ifname_policy=<replaceable>policy1</replaceable>[,<replaceable>policy2</replaceable>,…][,<replaceable>MAC</replaceable>]</varname></term>
|
2021-12-14 02:29:08 +00:00
|
|
|
<listitem>
|
|
|
|
<para>Specifies naming policies applied when renaming network interfaces. Takes a list of
|
|
|
|
policies and an optional MAC address separated with comma. Each policy value must be one of
|
|
|
|
the policies understood by the <varname>NamePolicy=</varname> setting in .link files, e.g.
|
|
|
|
<literal>onboard</literal> or <literal>path</literal>. See
|
|
|
|
<citerefentry><refentrytitle>systemd.link</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
|
|
|
for more details. When the MAC address is specified, the policies are applied to the
|
|
|
|
interface which has the address. When no MAC address is specified, the policies are applied
|
2021-12-16 08:56:13 +00:00
|
|
|
to all interfaces. This kernel command line argument can be specified multiple times.</para>
|
|
|
|
|
|
|
|
<para>This argument is not directly read by <command>systemd-udevd</command>, but is instead
|
|
|
|
converted to a .link file by
|
|
|
|
<citerefentry><refentrytitle>systemd-network-generator.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
|
|
|
|
For this argument to take effect, <filename>systemd-network-generator.service</filename> must be
|
|
|
|
enabled.</para>
|
|
|
|
|
2021-12-14 02:29:08 +00:00
|
|
|
<para>Example:
|
2024-02-28 14:31:27 +00:00
|
|
|
<programlisting>net.ifname_policy=keep,kernel,path,slot,onboard,01:23:45:67:89:ab
|
|
|
|
net.ifname_policy=keep,kernel,path,slot,onboard,mac</programlisting>
|
2021-12-14 02:29:08 +00:00
|
|
|
This is mostly equivalent to creating the following .link files:
|
|
|
|
<programlisting># 91-name-policy-with-mac.link
|
|
|
|
[Match]
|
|
|
|
MACAddress=01:23:45:67:89:ab
|
|
|
|
|
|
|
|
[Link]
|
|
|
|
NamePolicy=keep kernel path slot onboard
|
|
|
|
AlternativeNamePolicy=path slot onboard</programlisting>
|
|
|
|
and
|
|
|
|
<programlisting># 92-name-policy-for-all.link
|
|
|
|
[Match]
|
|
|
|
OriginalName=*
|
|
|
|
|
|
|
|
[Link]
|
|
|
|
NamePolicy=keep kernel path slot onboard mac
|
|
|
|
AlternativeNamePolicy=path slot onboard mac</programlisting>
|
|
|
|
</para>
|
2023-08-22 16:52:36 +00:00
|
|
|
|
|
|
|
<xi:include href="version-info.xml" xpointer="v250"/>
|
2021-12-14 02:29:08 +00:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2010-05-24 15:00:15 +00:00
|
|
|
</variablelist>
|
2019-05-09 10:34:30 +00:00
|
|
|
<!-- when adding entries here, consider also adding them in kernel-command-line.xml -->
|
|
|
|
</refsect1>
|
2005-08-30 21:30:52 +00:00
|
|
|
|
2010-05-24 15:00:15 +00:00
|
|
|
<refsect1>
|
|
|
|
<title>See Also</title>
|
2023-12-22 18:09:32 +00:00
|
|
|
<para><simplelist type="inline">
|
|
|
|
<member><citerefentry><refentrytitle>udev.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry></member>
|
|
|
|
<member><citerefentry><refentrytitle>udev</refentrytitle><manvolnum>7</manvolnum></citerefentry></member>
|
|
|
|
<member><citerefentry><refentrytitle>udevadm</refentrytitle><manvolnum>8</manvolnum></citerefentry></member>
|
|
|
|
</simplelist></para>
|
2010-05-24 15:00:15 +00:00
|
|
|
</refsect1>
|
|
|
|
</refentry>
|