summaryrefslogtreecommitdiff
path: root/man/systemd.network.xml
diff options
context:
space:
mode:
authorYu Watanabe <watanabe.yu+github@gmail.com>2022-04-18 03:08:55 +0900
committerYu Watanabe <watanabe.yu+github@gmail.com>2022-04-18 04:30:49 +0900
commitcc9b6bdc96e157e6ee9e4dc1d0a304a9df601564 (patch)
tree02071b5fbd02a1a959e1fefbea7afe53ca88c243 /man/systemd.network.xml
parentbf93f24ad8743e1dae7d8629946df7325af2bef7 (diff)
downloadsystemd-cc9b6bdc96e157e6ee9e4dc1d0a304a9df601564.tar.gz
man: recommend that .network or friends should have a numeric prefix
Closes #23105.
Diffstat (limited to 'man/systemd.network.xml')
-rw-r--r--man/systemd.network.xml15
1 files changed, 10 insertions, 5 deletions
diff --git a/man/systemd.network.xml b/man/systemd.network.xml
index daab872fdd..4f1c9e4b27 100644
--- a/man/systemd.network.xml
+++ b/man/systemd.network.xml
@@ -42,8 +42,12 @@
<filename>/usr/local/lib/systemd/network</filename>, the volatile runtime network directory
<filename>/run/systemd/network</filename> and the local administration network directory
<filename>/etc/systemd/network</filename>. All configuration files are collectively sorted and
- processed in lexical order, regardless of the directories in which they live. However, files with
- identical filenames replace each other. Files in <filename>/etc/</filename> have the highest
+ processed in alphanumeric order, regardless of the directories in which they live. However, files
+ with identical filenames replace each other. It is recommended that each filename is prefixed with
+ a number (e.g. <filename>10-eth0.network</filename>). Otherwise, the default
+ <filename>.network</filename> files or those generated by
+ <citerefentry><refentrytitle>systemd-network-generator.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
+ may take precedence over user configured files. Files in <filename>/etc/</filename> have the highest
priority, files in <filename>/run/</filename> take precedence over files with the same name under
<filename>/usr/</filename>. This can be used to override a system-supplied configuration file with
a local file if needed. As a special case, an empty file (file size 0) or symlink with the same
@@ -69,9 +73,9 @@
<title>[Match] Section Options</title>
<para>The network file contains a [Match] section, which determines if a given network file may
- be applied to a given device; and a [Network] section specifying how the device should be
- configured. The first (in lexical order) of the network files that matches a given device is
- applied, all later files are ignored, even if they match as well.</para>
+ be applied to a given interface; and a [Network] section specifying how the interface should be
+ configured. The first (in alphanumeric order) of the network files that matches a given interface
+ is applied, all later files are ignored, even if they match as well.</para>
<para>A network file is said to match a network interface if all matches specified by the [Match]
section are satisfied. When a network file does not contain valid settings in [Match] section, then
@@ -4774,6 +4778,7 @@ Xfrm=xfrm0</programlisting>
<citerefentry><refentrytitle>systemd-networkd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd.link</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd.netdev</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
+ <citerefentry><refentrytitle>systemd-network-generator.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd-resolved.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
</para>
</refsect1>