diff options
author | Jan Synacek <jsynacek@redhat.com> | 2019-10-07 10:03:07 +0200 |
---|---|---|
committer | Yu Watanabe <watanabe.yu+github@gmail.com> | 2019-10-14 22:01:11 +0900 |
commit | 4801d8afe2ff1c1c075c9f0bc5631612172e0bb7 (patch) | |
tree | 320a1e198b9bfc33aa7024ee0dfc231fa7f1ef0a /man | |
parent | 55d3fdcf5e9f6ceb9fc1a5f93120305f20abf690 (diff) | |
download | systemd-4801d8afe2ff1c1c075c9f0bc5631612172e0bb7.tar.gz |
udev: introduce CONST key name
Currently, there is no way to match against system-wide constants, such
as architecture or virtualization type, without forking helper binaries.
That potentially results in a huge number of spawned processes which
output always the same answer.
This patch introduces a special CONST keyword which takes a hard-coded
string as its key and returns a value assigned to that key. Currently
implemented are CONST{arch} and CONST{virt}, which can be used to match
against the system's architecture and virtualization type.
Diffstat (limited to 'man')
-rw-r--r-- | man/udev.xml | 26 |
1 files changed, 26 insertions, 0 deletions
diff --git a/man/udev.xml b/man/udev.xml index 98d17bbb54..09254f818e 100644 --- a/man/udev.xml +++ b/man/udev.xml @@ -237,6 +237,32 @@ </varlistentry> <varlistentry> + <term><varname>CONST{<replaceable>key</replaceable>}</varname></term> + <listitem> + <para>Match against a system-wide constant. Supported keys are:</para> + <variablelist> + <varlistentry> + <term><literal>arch</literal></term> + <listitem> + <para>System's architecture. See <option>ConditionArchitecture=</option> in + <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry> + for possible values.</para> + </listitem> + </varlistentry> + <varlistentry> + <term><literal>virt</literal></term> + <listitem> + <para>System's virtualization environment. See + <citerefentry><refentrytitle>systemd-detect-virt</refentrytitle><manvolnum>1</manvolnum></citerefentry> + for possible values.</para> + </listitem> + </varlistentry> + </variablelist> + <para>Unknown keys will never match.</para> + </listitem> + </varlistentry> + + <varlistentry> <term><varname>TAG</varname></term> <listitem> <para>Match against a device tag.</para> |