diff options
-rw-r--r-- | man/coredumpctl.xml | 2 | ||||
-rw-r--r-- | man/environment.d.xml | 2 | ||||
-rw-r--r-- | man/systemd-analyze.xml | 6 | ||||
-rw-r--r-- | man/systemd-cat.xml | 2 | ||||
-rw-r--r-- | man/systemd-nspawn.xml | 2 | ||||
-rw-r--r-- | man/systemd.automount.xml | 2 | ||||
-rw-r--r-- | man/systemd.device.xml | 2 | ||||
-rw-r--r-- | man/systemd.link.xml | 2 | ||||
-rw-r--r-- | man/systemd.mount.xml | 2 | ||||
-rw-r--r-- | man/systemd.net-naming-scheme.xml | 4 | ||||
-rw-r--r-- | man/systemd.offline-updates.xml | 12 | ||||
-rw-r--r-- | man/systemd.service.xml | 4 | ||||
-rw-r--r-- | man/systemd.swap.xml | 2 | ||||
-rw-r--r-- | man/systemd.unit.xml | 10 | ||||
-rw-r--r-- | man/tmpfiles.d.xml | 2 | ||||
-rw-r--r-- | man/user@.service.xml | 28 | ||||
-rwxr-xr-x | tools/make-directive-index.py | 4 |
17 files changed, 44 insertions, 44 deletions
diff --git a/man/coredumpctl.xml b/man/coredumpctl.xml index 2b0f62a28d..4e99bc0d69 100644 --- a/man/coredumpctl.xml +++ b/man/coredumpctl.xml @@ -321,7 +321,7 @@ <example> <title>Extract the last core dump of /usr/bin/bar to a file named - <filename noindex="true">bar.coredump</filename></title> + <filename index="false">bar.coredump</filename></title> <programlisting># coredumpctl -o bar.coredump dump /usr/bin/bar</programlisting> </example> diff --git a/man/environment.d.xml b/man/environment.d.xml index 702154837b..69c156aacb 100644 --- a/man/environment.d.xml +++ b/man/environment.d.xml @@ -75,7 +75,7 @@ <title>Example</title> <example> <title>Setup environment to allow access to a program installed in - <filename noindex='true'>/opt/foo</filename></title> + <filename index="false">/opt/foo</filename></title> <para><filename>/etc/environment.d/60-foo.conf</filename>: </para> diff --git a/man/systemd-analyze.xml b/man/systemd-analyze.xml index dcb7cf29c1..911a00bc02 100644 --- a/man/systemd-analyze.xml +++ b/man/systemd-analyze.xml @@ -348,8 +348,8 @@ DATAERR 65 BSD <refsect2> <title><command>systemd-analyze condition <replaceable>CONDITION</replaceable>...</command></title> - <para>This command will evaluate <varname noindex='true'>Condition*=...</varname> and - <varname noindex='true'>Assert*=...</varname> assignments, and print their values, and + <para>This command will evaluate <varname index="false">Condition*=...</varname> and + <varname index="false">Assert*=...</varname> assignments, and print their values, and the resulting value of the combined condition set. See <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry> for a list of available conditions and asserts.</para> @@ -602,7 +602,7 @@ Service b@0.service not loaded, b.socket cannot be started. policy is not validated too.</para> <example> - <title>Analyze <filename noindex="true">systemd-logind.service</filename></title> + <title>Analyze <filename index="false">systemd-logind.service</filename></title> <programlisting>$ systemd-analyze security --no-pager systemd-logind.service NAME DESCRIPTION EXPOSURE diff --git a/man/systemd-cat.xml b/man/systemd-cat.xml index f3d6f3785f..96d3072a1f 100644 --- a/man/systemd-cat.xml +++ b/man/systemd-cat.xml @@ -140,7 +140,7 @@ <example> <title>Invoke a program</title> - <para>This calls <filename noindex='true'>/bin/ls</filename> + <para>This calls <filename index="false">/bin/ls</filename> with standard output and error connected to the journal:</para> <programlisting># systemd-cat ls</programlisting> diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml index 92987ff32f..f5d42350dd 100644 --- a/man/systemd-nspawn.xml +++ b/man/systemd-nspawn.xml @@ -1366,7 +1366,7 @@ # systemd-nspawn -bD /var/lib/machines/f&fedora_latest_version;</programlisting> <para>This installs a minimal Fedora distribution into the - directory <filename noindex='true'>/var/lib/machines/f&fedora_latest_version;</filename> + directory <filename index="false">/var/lib/machines/f&fedora_latest_version;</filename> and then boots an OS in a namespace container in it. Because the installation is located underneath the standard <filename>/var/lib/machines/</filename> directory, it is also possible to start the machine using diff --git a/man/systemd.automount.xml b/man/systemd.automount.xml index 75302e07e9..f2ed761021 100644 --- a/man/systemd.automount.xml +++ b/man/systemd.automount.xml @@ -40,7 +40,7 @@ are configured in the <literal>[Automount]</literal> section.</para> <para>Automount units must be named after the automount directories they control. Example: the automount point - <filename noindex='true'>/home/lennart</filename> must be configured in a unit file + <filename index="false">/home/lennart</filename> must be configured in a unit file <filename>home-lennart.automount</filename>. For details about the escaping logic used to convert a file system path to a unit name see <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>. Note that diff --git a/man/systemd.device.xml b/man/systemd.device.xml index ff7ab9ccce..ae786a3298 100644 --- a/man/systemd.device.xml +++ b/man/systemd.device.xml @@ -51,7 +51,7 @@ <para>Device units are named after the <filename>/sys</filename> and <filename>/dev</filename> paths they control. Example: the - device <filename noindex='true'>/dev/sda5</filename> is exposed in + device <filename index="false">/dev/sda5</filename> is exposed in systemd as <filename>dev-sda5.device</filename>. For details about the escaping logic used to convert a file system path to a unit name see diff --git a/man/systemd.link.xml b/man/systemd.link.xml index 5013e7e9b5..59d1434694 100644 --- a/man/systemd.link.xml +++ b/man/systemd.link.xml @@ -709,7 +709,7 @@ ID_NET_LINK_FILE=/usr/lib/systemd/network/99-default.link </programlisting> <para>In this case, the interface was already renamed, so the <option>keep</option> policy specified as - the first option in <filename noindex='true'>99-default.link</filename> means that the existing name is + the first option in <filename index="false">99-default.link</filename> means that the existing name is preserved. If <option>keep</option> was removed, or if were in boot before the renaming has happened, we might get the following instead:</para> diff --git a/man/systemd.mount.xml b/man/systemd.mount.xml index a72a33240d..b2c9d60681 100644 --- a/man/systemd.mount.xml +++ b/man/systemd.mount.xml @@ -60,7 +60,7 @@ must be run as UID 0.</para> <para>Mount units must be named after the mount point directories they control. Example: the mount point <filename - noindex='true'>/home/lennart</filename> must be configured in a unit file <filename>home-lennart.mount</filename>. + index="false">/home/lennart</filename> must be configured in a unit file <filename>home-lennart.mount</filename>. For details about the escaping logic used to convert a file system path to a unit name, see <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>. Note that mount units cannot be templated, nor is possible to add multiple names to a mount unit by creating additional symlinks to diff --git a/man/systemd.net-naming-scheme.xml b/man/systemd.net-naming-scheme.xml index 419fed62ea..ec3b8671f2 100644 --- a/man/systemd.net-naming-scheme.xml +++ b/man/systemd.net-naming-scheme.xml @@ -300,7 +300,7 @@ again. Previously, this naming policy applied implicitly, and now it must be explicitly requested. Effectively, this means that network devices will be renamed according to the configuration, even if they have been renamed already, if <constant>keep</constant> is not - specified as the naming policy in the <filename noindex='true'>.link</filename> file. See + specified as the naming policy in the <filename index="false">.link</filename> file. See <citerefentry><refentrytitle>systemd.link</refentrytitle><manvolnum>5</manvolnum></citerefentry> for a description of <varname>NamePolicy=</varname>.</para></listitem> </varlistentry> @@ -310,7 +310,7 @@ <listitem><para><option>MACAddressPolicy=persistent</option> was extended to set MAC addresses based on the device name. Previously addresses were only based on the - <varname noindex='true'>ID_NET_NAME_*</varname> attributes, which meant that interface names would + <varname index="false">ID_NET_NAME_*</varname> attributes, which meant that interface names would never be generated for virtual devices. Now a persistent address will be generated for most devices, including in particular bridges.</para> diff --git a/man/systemd.offline-updates.xml b/man/systemd.offline-updates.xml index 06390669de..89c12b598b 100644 --- a/man/systemd.offline-updates.xml +++ b/man/systemd.offline-updates.xml @@ -35,13 +35,13 @@ <listitem> <para>The package manager prepares system updates by downloading all (RPM or DEB or whatever) packages to update off-line in a special directory - <filename noindex="true">/var/lib/system-update</filename> (or + <filename index="false">/var/lib/system-update</filename> (or another directory of the package/upgrade manager's choice).</para> </listitem> <listitem> <para>When the user OK'ed the update, the symlink <filename>/system-update</filename> is - created that points to <filename noindex="true">/var/lib/system-update</filename> (or + created that points to <filename index="false">/var/lib/system-update</filename> (or wherever the directory with the upgrade files is located) and the system is rebooted. This symlink is in the root directory, since we need to check for it very early at boot, at a time where <filename>/var</filename> is not available yet.</para> @@ -106,12 +106,12 @@ <orderedlist> <listitem> <para>To make things a bit more robust we recommend hooking the update script into - <filename>system-update.target</filename> via a <filename noindex='true'>.wants/</filename> + <filename>system-update.target</filename> via a <filename index="false">.wants/</filename> symlink in the distribution package, rather than depending on <command>systemctl enable</command> in the postinst scriptlets of your package. More specifically, for your update script create a .service file, without [Install] section, and then add a symlink like - <filename noindex='true'>/usr/lib/systemd/system-update.target.wants/foobar.service</filename> - → <filename noindex='true'>../foobar.service</filename> to your package.</para> + <filename index="false">/usr/lib/systemd/system-update.target.wants/foobar.service</filename> + → <filename index="false">../foobar.service</filename> to your package.</para> </listitem> <listitem> @@ -144,7 +144,7 @@ <varname>Wants=system-update-pre.target</varname> and <varname>Before=system-update-pre.target</varname> and add a symlink to that file under - <filename noindex='true'>/usr/lib/systemd/system-update.target.wants</filename> + <filename index="false">/usr/lib/systemd/system-update.target.wants</filename> .</para> </listitem> </orderedlist> diff --git a/man/systemd.service.xml b/man/systemd.service.xml index f57e37ca5b..f76005a296 100644 --- a/man/systemd.service.xml +++ b/man/systemd.service.xml @@ -1329,8 +1329,8 @@ WantedBy=multi-user.target</programlisting> <para><varname>Type=</varname><option>oneshot</option> are the only service units that may have more than one <varname>ExecStart=</varname> specified. For units with multiple - commands (<varname noindex="true">Type=oneshot</varname>), all commands will be run again.</para> - <para> For <varname noindex="true">Type=oneshot</varname>, <varname>Restart=</varname><option>always</option> + commands (<varname index="false">Type=oneshot</varname>), all commands will be run again.</para> + <para> For <varname index="false">Type=oneshot</varname>, <varname>Restart=</varname><option>always</option> and <varname>Restart=</varname><option>on-success</option> are <emphasis>not</emphasis> allowed.</para> </example> diff --git a/man/systemd.swap.xml b/man/systemd.swap.xml index 23547bb273..190fc388c0 100644 --- a/man/systemd.swap.xml +++ b/man/systemd.swap.xml @@ -54,7 +54,7 @@ unit.</para> <para>Swap units must be named after the devices or files they control. Example: the swap device <filename - noindex='true'>/dev/sda5</filename> must be configured in a unit file <filename>dev-sda5.swap</filename>. For + index="false">/dev/sda5</filename> must be configured in a unit file <filename>dev-sda5.swap</filename>. For details about the escaping logic used to convert a file system path to a unit name, see <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>. Note that swap units cannot be templated, nor is possible to add multiple names to a swap unit by creating additional symlinks to diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index d6ff6cf9cb..b7bae08c69 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -246,7 +246,7 @@ escaping is used, in order to map strings containing arbitrary byte values (except NUL) into valid unit names and their restricted character set. A common special case are unit names that reflect paths to objects in the file system hierarchy. Example: a device unit <filename>dev-sda.device</filename> refers to a device with the device - node <filename noindex='true'>/dev/sda</filename> in the file system.</para> + node <filename index="false">/dev/sda</filename> in the file system.</para> <para>The escaping algorithm operates as follows: given a string, any <literal>/</literal> character is replaced by <literal>-</literal>, and all other characters which are not ASCII alphanumerics or <literal>_</literal> are @@ -435,7 +435,7 @@ <entry>Units of packages that have been installed in the home directory (<varname>$XDG_DATA_HOME</varname> is used if set, <filename>~/.local/share</filename> otherwise)</entry> </row> <row> - <entry><filename>$dir/systemd/user</filename> for each <varname noindex='true'>$dir</varname> in <varname>$XDG_DATA_DIRS</varname></entry> + <entry><filename>$dir/systemd/user</filename> for each <varname index="false">$dir</varname> in <varname>$XDG_DATA_DIRS</varname></entry> <entry>Additional locations for installed user units, one for each entry in <varname>$XDG_DATA_DIRS</varname></entry> </row> <row> @@ -1026,8 +1026,8 @@ <refsect2> <title>Conditions and Asserts</title> - <para>Unit files may also include a number of <varname noindex="true">Condition…=</varname> and - <varname noindex="true">Assert…=</varname> settings. Before the unit is started, systemd will verify + <para>Unit files may also include a number of <varname index="false">Condition…=</varname> and + <varname index="false">Assert…=</varname> settings. Before the unit is started, systemd will verify that the specified conditions are true. If not, the starting of the unit will be (mostly silently) skipped. Failing conditions will not result in the unit being moved into the <literal>failed</literal> state. The conditions are checked at the time the queued start job is to be executed. The ordering @@ -1731,7 +1731,7 @@ Note that this setting is <emphasis>not</emphasis> influenced by the <varname>Us <row> <entry><literal>%L</literal></entry> <entry>Log directory root</entry> - <entry>This is either <filename>/var/log</filename> (for the system manager) or the path <literal>$XDG_CONFIG_HOME</literal> resolves to with <filename noindex='true'>/log</filename> appended (for user managers).</entry> + <entry>This is either <filename>/var/log</filename> (for the system manager) or the path <literal>$XDG_CONFIG_HOME</literal> resolves to with <filename index="false">/log</filename> appended (for user managers).</entry> </row> <row> <entry><literal>%m</literal></entry> diff --git a/man/tmpfiles.d.xml b/man/tmpfiles.d.xml index aae63b7591..8a3dde3644 100644 --- a/man/tmpfiles.d.xml +++ b/man/tmpfiles.d.xml @@ -654,7 +654,7 @@ w- /proc/sys/vm/swappiness - - - - 10</programlisting></para> <row> <entry><literal>%L</literal></entry> <entry>System or user log directory</entry> - <entry>In <option>--user</option> mode, this is the same as <varname>$XDG_CONFIG_HOME</varname> with <filename noindex='true'>/log</filename> appended, and <filename>/var/log</filename> otherwise.</entry> + <entry>In <option>--user</option> mode, this is the same as <varname>$XDG_CONFIG_HOME</varname> with <filename index="false">/log</filename> appended, and <filename>/var/log</filename> otherwise.</entry> </row> <row> <entry><literal>%m</literal></entry> diff --git a/man/user@.service.xml b/man/user@.service.xml index e748c03b88..81a6fef4ba 100644 --- a/man/user@.service.xml +++ b/man/user@.service.xml @@ -68,16 +68,16 @@ different levels. As described in the previous section, <filename>user.slice</filename> contains processes of all users, so any resource limits on that slice apply to all users together. The usual way to configure them would be through drop-ins, e.g. <filename - noindex='true'>/etc/systemd/system/user.slice.d/resources.conf</filename>. + index="false">/etc/systemd/system/user.slice.d/resources.conf</filename>. </para> <para>The processes of a single user are collected under <filename>user-<replaceable>UID</replaceable>.slice</filename>. Resource limits for that user can be configured through drop-ins for that unit, e.g. <filename - noindex='true'>/etc/systemd/system/user-1000.slice.d/resources.conf</filename>. If the limits + index="false">/etc/systemd/system/user-1000.slice.d/resources.conf</filename>. If the limits should apply to all users instead, they may be configured through drop-ins for the truncated unit name, <filename>user-.slice</filename>. For example, configuration in <filename - noindex='true'>/etc/systemd/system/user-.slice.d/resources.conf</filename> is included in all + index="false">/etc/systemd/system/user-.slice.d/resources.conf</filename> is included in all <filename>user-<replaceable>UID</replaceable>.slice</filename> units, see <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry> for a discussion of the drop-in mechanism.</para> @@ -141,20 +141,20 @@ Control group /: │ └─6706 /usr/bin/sleep 30 …</programlisting> <para>User with UID 1000 is logged in using <command>gdm</command> (<filename - noindex='true'>session-4.scope</filename>) and + index="false">session-4.scope</filename>) and <citerefentry><refentrytitle>ssh</refentrytitle><manvolnum>1</manvolnum></citerefentry> - (<filename noindex='true'>session-19.scope</filename>), and also has a user manager instance - running (<filename noindex='true'>user@1000.service</filename>). User with UID 1001 is logged - in using <command>ssh</command> (<filename noindex='true'>session-20.scope</filename>) and + (<filename index="false">session-19.scope</filename>), and also has a user manager instance + running (<filename index="false">user@1000.service</filename>). User with UID 1001 is logged + in using <command>ssh</command> (<filename index="false">session-20.scope</filename>) and also has a user manager instance running (<filename - noindex='true'>user@1001.service</filename>). Those are all (leaf) system units, and form - part of the slice hierarchy, with <filename noindex='true'>user-1000.slice</filename> and - <filename noindex='true'>user-1001.slice</filename> below <filename - noindex='true'>user.slice</filename>. User units are visible below the + index="false">user@1001.service</filename>). Those are all (leaf) system units, and form + part of the slice hierarchy, with <filename index="false">user-1000.slice</filename> and + <filename index="false">user-1001.slice</filename> below <filename + index="false">user.slice</filename>. User units are visible below the <filename>user@.service</filename> instances (<filename - noindex='true'>pulseaudio.service</filename>, <filename - noindex='true'>gnome-terminal-server.service</filename>, <filename - noindex='true'>init.scope</filename>, <filename noindex='true'>sleep.service</filename>). + index="false">pulseaudio.service</filename>, <filename + index="false">gnome-terminal-server.service</filename>, <filename + index="false">init.scope</filename>, <filename index="false">sleep.service</filename>). </para> </example> diff --git a/tools/make-directive-index.py b/tools/make-directive-index.py index 9d9448703f..2bc178de50 100755 --- a/tools/make-directive-index.py +++ b/tools/make-directive-index.py @@ -204,7 +204,7 @@ def _extract_directives(directive_groups, formatting, page): for name in t.iterfind(xpath): if absolute_only and not (name.text and name.text.startswith('/')): continue - if name.attrib.get('noindex'): + if name.attrib.get('index') == 'false': continue name.tail = '' if name.text: @@ -228,7 +228,7 @@ def _extract_directives(directive_groups, formatting, page): storfile = directive_groups['constants'] for name in t.iterfind('.//constant'): - if name.attrib.get('noindex'): + if name.attrib.get('index') == 'false': continue name.tail = '' if name.text.startswith('('): # a cast, strip it |