doc: correct orthography, word forms and missing/extraneous words
This commit is contained in:
parent
b938cb902c
commit
a8eaaee72a
18
NEWS
18
NEWS
|
@ -117,7 +117,7 @@ CHANGES WITH 227:
|
||||||
|
|
||||||
* File descriptors passed during socket activation may now be
|
* File descriptors passed during socket activation may now be
|
||||||
named. A new API sd_listen_fds_with_names() is added to
|
named. A new API sd_listen_fds_with_names() is added to
|
||||||
access the names. The default names may be overriden,
|
access the names. The default names may be overridden,
|
||||||
either in the .socket file using the FileDescriptorName=
|
either in the .socket file using the FileDescriptorName=
|
||||||
parameter, or by passing FDNAME= when storing the file
|
parameter, or by passing FDNAME= when storing the file
|
||||||
descriptors using sd_notify().
|
descriptors using sd_notify().
|
||||||
|
@ -1209,7 +1209,7 @@ CHANGES WITH 218:
|
||||||
|
|
||||||
* journalctl gained two new commands --vacuum-size= and
|
* journalctl gained two new commands --vacuum-size= and
|
||||||
--vacuum-time= to delete old journal files until the
|
--vacuum-time= to delete old journal files until the
|
||||||
remaining ones take up no more the specified size on disk,
|
remaining ones take up no more than the specified size on disk,
|
||||||
or are not older than the specified time.
|
or are not older than the specified time.
|
||||||
|
|
||||||
* A new, native PPPoE library has been added to sd-network,
|
* A new, native PPPoE library has been added to sd-network,
|
||||||
|
@ -1303,7 +1303,7 @@ CHANGES WITH 218:
|
||||||
a fixed machine ID for subsequent boots.
|
a fixed machine ID for subsequent boots.
|
||||||
|
|
||||||
* networkd's .netdev files now provide a large set of
|
* networkd's .netdev files now provide a large set of
|
||||||
configuration parameters for VXLAN devices. Similar, the
|
configuration parameters for VXLAN devices. Similarly, the
|
||||||
bridge port cost parameter is now configurable in .network
|
bridge port cost parameter is now configurable in .network
|
||||||
files. There's also new support for configuring IP source
|
files. There's also new support for configuring IP source
|
||||||
routing. networkd .link files gained support for a new
|
routing. networkd .link files gained support for a new
|
||||||
|
@ -1636,7 +1636,7 @@ CHANGES WITH 216:
|
||||||
|
|
||||||
* .socket units gained a new DeferAcceptSec= setting that
|
* .socket units gained a new DeferAcceptSec= setting that
|
||||||
controls the kernels' TCP_DEFER_ACCEPT sockopt for
|
controls the kernels' TCP_DEFER_ACCEPT sockopt for
|
||||||
TCP. Similar, support for controlling TCP keep-alive
|
TCP. Similarly, support for controlling TCP keep-alive
|
||||||
settings has been added (KeepAliveTimeSec=,
|
settings has been added (KeepAliveTimeSec=,
|
||||||
KeepAliveIntervalSec=, KeepAliveProbes=). Also, support for
|
KeepAliveIntervalSec=, KeepAliveProbes=). Also, support for
|
||||||
turning off Nagle's algorithm on TCP has been added
|
turning off Nagle's algorithm on TCP has been added
|
||||||
|
@ -1852,7 +1852,7 @@ CHANGES WITH 215:
|
||||||
* tmpfiles learnt a new "L+" directive which creates a symlink
|
* tmpfiles learnt a new "L+" directive which creates a symlink
|
||||||
but (unlike "L") deletes a pre-existing file first, should
|
but (unlike "L") deletes a pre-existing file first, should
|
||||||
it already exist and not already be the correct
|
it already exist and not already be the correct
|
||||||
symlink. Similar, "b+", "c+" and "p+" directives have been
|
symlink. Similarly, "b+", "c+" and "p+" directives have been
|
||||||
added as well, which create block and character devices, as
|
added as well, which create block and character devices, as
|
||||||
well as fifos in the filesystem, possibly removing any
|
well as fifos in the filesystem, possibly removing any
|
||||||
pre-existing files of different types.
|
pre-existing files of different types.
|
||||||
|
@ -2035,14 +2035,14 @@ CHANGES WITH 214:
|
||||||
CAP_NET_BROADCAST, CAP_NET_RAW capabilities though, but
|
CAP_NET_BROADCAST, CAP_NET_RAW capabilities though, but
|
||||||
loses the ability to write to files owned by root this way.
|
loses the ability to write to files owned by root this way.
|
||||||
|
|
||||||
* Similar, systemd-resolved now runs under its own
|
* Similarly, systemd-resolved now runs under its own
|
||||||
"systemd-resolve" user with no capabilities remaining.
|
"systemd-resolve" user with no capabilities remaining.
|
||||||
|
|
||||||
* Similar, systemd-bus-proxyd now runs under its own
|
* Similarly, systemd-bus-proxyd now runs under its own
|
||||||
"systemd-bus-proxy" user with only CAP_IPC_OWNER remaining.
|
"systemd-bus-proxy" user with only CAP_IPC_OWNER remaining.
|
||||||
|
|
||||||
* systemd-networkd gained support for setting up "veth"
|
* systemd-networkd gained support for setting up "veth"
|
||||||
virtual ethernet devices for container connectivity, as well
|
virtual Ethernet devices for container connectivity, as well
|
||||||
as GRE and VTI tunnels.
|
as GRE and VTI tunnels.
|
||||||
|
|
||||||
* systemd-networkd will no longer automatically attempt to
|
* systemd-networkd will no longer automatically attempt to
|
||||||
|
@ -2744,7 +2744,7 @@ CHANGES WITH 209:
|
||||||
* The configuration of network interface naming rules for
|
* The configuration of network interface naming rules for
|
||||||
"permanent interface names" has changed: a new NamePolicy=
|
"permanent interface names" has changed: a new NamePolicy=
|
||||||
setting in the [Link] section of .link files determines the
|
setting in the [Link] section of .link files determines the
|
||||||
priority of possible naming schemes (onboard, slot, mac,
|
priority of possible naming schemes (onboard, slot, MAC,
|
||||||
path). The default value of this setting is determined by
|
path). The default value of this setting is determined by
|
||||||
/usr/lib/net/links/99-default.link. Old
|
/usr/lib/net/links/99-default.link. Old
|
||||||
80-net-name-slot.rules udev configuration file has been
|
80-net-name-slot.rules udev configuration file has been
|
||||||
|
|
2
TODO
2
TODO
|
@ -876,7 +876,7 @@ Features:
|
||||||
- add Scope= parsing option for [Network]
|
- add Scope= parsing option for [Network]
|
||||||
- properly handle routerless dhcp leases
|
- properly handle routerless dhcp leases
|
||||||
- add more attribute support for SIT tunnel
|
- add more attribute support for SIT tunnel
|
||||||
- work with non-ethernet devices
|
- work with non-Ethernet devices
|
||||||
- add support for more bond options
|
- add support for more bond options
|
||||||
|
|
||||||
* networkd-wait-online:
|
* networkd-wait-online:
|
||||||
|
|
|
@ -68,7 +68,7 @@
|
||||||
system.</para>
|
system.</para>
|
||||||
|
|
||||||
<para><command>bootctl status</command> checks and prints the
|
<para><command>bootctl status</command> checks and prints the
|
||||||
currently installed versions of the boot loader binaries and the
|
currently installed versions of the boot loader binaries and
|
||||||
all current EFI boot variables.</para>
|
all current EFI boot variables.</para>
|
||||||
|
|
||||||
<para><command>bootctl update</command> updates all installed
|
<para><command>bootctl update</command> updates all installed
|
||||||
|
|
|
@ -231,7 +231,7 @@
|
||||||
be augmented with data from
|
be augmented with data from
|
||||||
<filename>/proc</filename>. When this is turned on, the data
|
<filename>/proc</filename>. When this is turned on, the data
|
||||||
shown is possibly inconsistent, as the data read from
|
shown is possibly inconsistent, as the data read from
|
||||||
<filename>/proc</filename> might be more recent than rest of
|
<filename>/proc</filename> might be more recent than the rest of
|
||||||
the credential information. Defaults to <literal>yes</literal>.</para>
|
the credential information. Defaults to <literal>yes</literal>.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
@ -281,7 +281,7 @@
|
||||||
<replaceable>SERVICE</replaceable> is specified, show messages
|
<replaceable>SERVICE</replaceable> is specified, show messages
|
||||||
to or from this peer, identified by its well-known or unique
|
to or from this peer, identified by its well-known or unique
|
||||||
name. Otherwise, show all messages on the bus. Use Ctrl-C to
|
name. Otherwise, show all messages on the bus. Use Ctrl-C to
|
||||||
terminate dump.</para></listitem>
|
terminate the dump.</para></listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
|
@ -344,7 +344,7 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><command>set-property</command> <arg choice="plain"><replaceable>SERVICE</replaceable></arg> <arg choice="plain"><replaceable>OBJECT</replaceable></arg> <arg choice="plain"><replaceable>INTERFACE</replaceable></arg> <arg choice="plain"><replaceable>PROPERTY</replaceable></arg> <arg choice="plain"><replaceable>SIGNATURE</replaceable></arg> <arg choice="plain" rep="repeat"><replaceable>ARGUMENT</replaceable></arg></term>
|
<term><command>set-property</command> <arg choice="plain"><replaceable>SERVICE</replaceable></arg> <arg choice="plain"><replaceable>OBJECT</replaceable></arg> <arg choice="plain"><replaceable>INTERFACE</replaceable></arg> <arg choice="plain"><replaceable>PROPERTY</replaceable></arg> <arg choice="plain"><replaceable>SIGNATURE</replaceable></arg> <arg choice="plain" rep="repeat"><replaceable>ARGUMENT</replaceable></arg></term>
|
||||||
|
|
||||||
<listitem><para>Set the current value an object
|
<listitem><para>Set the current value of an object
|
||||||
property. Takes a service name, object path, interface name,
|
property. Takes a service name, object path, interface name,
|
||||||
property name, property signature, followed by a list of
|
property name, property signature, followed by a list of
|
||||||
parameters formatted as strings.</para></listitem>
|
parameters formatted as strings.</para></listitem>
|
||||||
|
@ -370,9 +370,9 @@
|
||||||
types, each parameter following the signature should simply be the
|
types, each parameter following the signature should simply be the
|
||||||
parameter's value formatted as string. Positive boolean values may
|
parameter's value formatted as string. Positive boolean values may
|
||||||
be formatted as <literal>true</literal>, <literal>yes</literal>,
|
be formatted as <literal>true</literal>, <literal>yes</literal>,
|
||||||
<literal>on</literal>, <literal>1</literal>; negative boolean
|
<literal>on</literal>, or <literal>1</literal>; negative boolean
|
||||||
values may be specified as <literal>false</literal>,
|
values may be specified as <literal>false</literal>,
|
||||||
<literal>no</literal>, <literal>off</literal>,
|
<literal>no</literal>, <literal>off</literal>, or
|
||||||
<literal>0</literal>. For arrays, a numeric argument for the
|
<literal>0</literal>. For arrays, a numeric argument for the
|
||||||
number of entries followed by the entries shall be specified. For
|
number of entries followed by the entries shall be specified. For
|
||||||
variants, the signature of the contents shall be specified,
|
variants, the signature of the contents shall be specified,
|
||||||
|
@ -456,7 +456,7 @@ ARRAY "s" {
|
||||||
of the <literal>org.freedesktop.systemd1</literal>
|
of the <literal>org.freedesktop.systemd1</literal>
|
||||||
service, and passes it two strings
|
service, and passes it two strings
|
||||||
<literal>cups.service</literal> and
|
<literal>cups.service</literal> and
|
||||||
<literal>replace</literal>. As result of the method
|
<literal>replace</literal>. As a result of the method
|
||||||
call, a single object path parameter is received and
|
call, a single object path parameter is received and
|
||||||
shown:</para>
|
shown:</para>
|
||||||
|
|
||||||
|
|
|
@ -98,7 +98,7 @@
|
||||||
<term><varname>Compress=</varname></term>
|
<term><varname>Compress=</varname></term>
|
||||||
|
|
||||||
<listitem><para>Controls compression for external
|
<listitem><para>Controls compression for external
|
||||||
storage. Takes a boolean argument, defaults to
|
storage. Takes a boolean argument, which defaults to
|
||||||
<literal>yes</literal>.</para>
|
<literal>yes</literal>.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
|
@ -160,10 +160,10 @@
|
||||||
at the beginning. This is different from the <option>--offset</option>
|
at the beginning. This is different from the <option>--offset</option>
|
||||||
option with respect to the sector numbers used in initialization vector
|
option with respect to the sector numbers used in initialization vector
|
||||||
(IV) calculation. Using <option>--offset</option> will shift the IV
|
(IV) calculation. Using <option>--offset</option> will shift the IV
|
||||||
calculation by the same negative amount. Hence, if <option>--offset n</option>,
|
calculation by the same negative amount. Hence, if <option>--offset n</option> is given,
|
||||||
sector n will get a sector number of 0 for the IV calculation.
|
sector n will get a sector number of 0 for the IV calculation.
|
||||||
Using <option>--skip</option> causes sector n to also be the first
|
Using <option>--skip</option> causes sector n to also be the first
|
||||||
sector of the mapped device, but with its number for IV generation is n.</para>
|
sector of the mapped device, but with its number for IV generation being n.</para>
|
||||||
|
|
||||||
<para>This option is only relevant for plain devices.</para>
|
<para>This option is only relevant for plain devices.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
|
@ -125,7 +125,7 @@
|
||||||
|
|
||||||
<!--
|
<!--
|
||||||
- helper template to do conflict resolution between various headings with the same inferred ID attribute/tag from the headerlink template
|
- helper template to do conflict resolution between various headings with the same inferred ID attribute/tag from the headerlink template
|
||||||
- this conflict resolution is necessary to prevent malformed HTML output (multiple id attributes with the same value)
|
- this conflict resolution is necessary to prevent malformed HTML output (multiple ID attributes with the same value)
|
||||||
- and it fixes xsltproc warnings during compilation of HTML man pages
|
- and it fixes xsltproc warnings during compilation of HTML man pages
|
||||||
-
|
-
|
||||||
- A simple top-to-bottom numbering scheme is implemented for nodes with the same ID value to derive unique ID values for HTML output.
|
- A simple top-to-bottom numbering scheme is implemented for nodes with the same ID value to derive unique ID values for HTML output.
|
||||||
|
|
|
@ -245,7 +245,7 @@
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><filename>/usr/lib/<replaceable>arch-id</replaceable></filename></term>
|
<term><filename>/usr/lib/<replaceable>arch-id</replaceable></filename></term>
|
||||||
<listitem><para>Location for placing dynamic libraries, also
|
<listitem><para>Location for placing dynamic libraries into, also
|
||||||
called <varname>$libdir</varname>. The architecture identifier
|
called <varname>$libdir</varname>. The architecture identifier
|
||||||
to use is defined on <ulink
|
to use is defined on <ulink
|
||||||
url="https://wiki.debian.org/Multiarch/Tuples">Multiarch
|
url="https://wiki.debian.org/Multiarch/Tuples">Multiarch
|
||||||
|
@ -405,7 +405,7 @@
|
||||||
when the user logs out. Usually, it is a better idea to use
|
when the user logs out. Usually, it is a better idea to use
|
||||||
memory mapped files in <filename>/run</filename> (for system
|
memory mapped files in <filename>/run</filename> (for system
|
||||||
programs) or <varname>$XDG_RUNTIME_DIR</varname> (for user
|
programs) or <varname>$XDG_RUNTIME_DIR</varname> (for user
|
||||||
programs) instead of POSIX shared memory segments, since those
|
programs) instead of POSIX shared memory segments, since these
|
||||||
directories are not world-writable and hence not vulnerable to
|
directories are not world-writable and hence not vulnerable to
|
||||||
security-sensitive name clashes.</para></listitem>
|
security-sensitive name clashes.</para></listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
@ -513,7 +513,7 @@
|
||||||
directory should have no effect on operation of programs,
|
directory should have no effect on operation of programs,
|
||||||
except for increased runtimes necessary to rebuild these
|
except for increased runtimes necessary to rebuild these
|
||||||
caches. If an application finds
|
caches. If an application finds
|
||||||
<varname>$XDG_CACHE_HOME</varname> set, is should use the
|
<varname>$XDG_CACHE_HOME</varname> set, it should use the
|
||||||
directory specified in it instead of this
|
directory specified in it instead of this
|
||||||
directory.</para></listitem>
|
directory.</para></listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
@ -525,7 +525,7 @@
|
||||||
new user is created, this directory will be empty or not exist
|
new user is created, this directory will be empty or not exist
|
||||||
at all. Applications should fall back to defaults should their
|
at all. Applications should fall back to defaults should their
|
||||||
configuration or state in this directory be missing. If an
|
configuration or state in this directory be missing. If an
|
||||||
application finds <varname>$XDG_CONFIG_HOME</varname> set, is
|
application finds <varname>$XDG_CONFIG_HOME</varname> set, it
|
||||||
should use the directory specified in it instead of this
|
should use the directory specified in it instead of this
|
||||||
directory.</para></listitem>
|
directory.</para></listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
@ -568,7 +568,7 @@
|
||||||
such as fonts or artwork. Usually, the precise location and
|
such as fonts or artwork. Usually, the precise location and
|
||||||
format of files stored below this directory is subject to
|
format of files stored below this directory is subject to
|
||||||
specifications that ensure interoperability. If an application
|
specifications that ensure interoperability. If an application
|
||||||
finds <varname>$XDG_DATA_HOME</varname> set, is should use the
|
finds <varname>$XDG_DATA_HOME</varname> set, it should use the
|
||||||
directory specified in it instead of this
|
directory specified in it instead of this
|
||||||
directory.</para></listitem>
|
directory.</para></listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
@ -618,7 +618,7 @@
|
||||||
|
|
||||||
<para>It is strongly recommended that <filename>/dev</filename> is
|
<para>It is strongly recommended that <filename>/dev</filename> is
|
||||||
the only location below which device nodes shall be placed.
|
the only location below which device nodes shall be placed.
|
||||||
Similar, <filename>/run</filename> shall be the only location to
|
Similarly, <filename>/run</filename> shall be the only location to
|
||||||
place sockets and FIFOs. Regular files, directories and symlinks
|
place sockets and FIFOs. Regular files, directories and symlinks
|
||||||
may be used in all directories.</para>
|
may be used in all directories.</para>
|
||||||
</refsect1>
|
</refsect1>
|
||||||
|
|
|
@ -34,7 +34,7 @@
|
||||||
|
|
||||||
<refsect1><title>Description</title>
|
<refsect1><title>Description</title>
|
||||||
<para>The hardware database is a key-value store for associating modalias-like keys to
|
<para>The hardware database is a key-value store for associating modalias-like keys to
|
||||||
udev-properties-like values. It is used primarily by udev to add the relevant properties
|
udev-property-like values. It is used primarily by udev to add the relevant properties
|
||||||
to matching devices, but it can also be queried directly.</para>
|
to matching devices, but it can also be queried directly.</para>
|
||||||
</refsect1>
|
</refsect1>
|
||||||
|
|
||||||
|
@ -57,7 +57,7 @@
|
||||||
associated key-value pairs. Every record in the hwdb starts with one or
|
associated key-value pairs. Every record in the hwdb starts with one or
|
||||||
more match strings, specifying a shell glob to compare the database
|
more match strings, specifying a shell glob to compare the database
|
||||||
lookup string against. Multiple match lines are specified in additional
|
lookup string against. Multiple match lines are specified in additional
|
||||||
consecutive lines. Every match line is compared individually, they are
|
consecutive lines. Every match line is compared individually, and they are
|
||||||
combined by OR. Every match line must start at the first character of
|
combined by OR. Every match line must start at the first character of
|
||||||
the line.</para>
|
the line.</para>
|
||||||
|
|
||||||
|
|
|
@ -82,7 +82,7 @@
|
||||||
matches apply to the same field, then they are automatically
|
matches apply to the same field, then they are automatically
|
||||||
matched as alternatives, i.e. the resulting output will show
|
matched as alternatives, i.e. the resulting output will show
|
||||||
entries matching any of the specified matches for the same
|
entries matching any of the specified matches for the same
|
||||||
field. Finally, the character <literal>+</literal> may appears
|
field. Finally, the character <literal>+</literal> may appear
|
||||||
as a separate word between other terms on the command line. This
|
as a separate word between other terms on the command line. This
|
||||||
causes all matches before and after to be combined in a
|
causes all matches before and after to be combined in a
|
||||||
disjunction (i.e. logical OR).</para>
|
disjunction (i.e. logical OR).</para>
|
||||||
|
@ -656,18 +656,18 @@
|
||||||
<listitem><para>Removes archived journal files until the disk
|
<listitem><para>Removes archived journal files until the disk
|
||||||
space they use falls below the specified size (specified with
|
space they use falls below the specified size (specified with
|
||||||
the usual <literal>K</literal>, <literal>M</literal>,
|
the usual <literal>K</literal>, <literal>M</literal>,
|
||||||
<literal>G</literal>, <literal>T</literal> suffixes), or all
|
<literal>G</literal> and <literal>T</literal> suffixes), or all
|
||||||
journal files contain no data older than the specified
|
journal files contain no data older than the specified
|
||||||
timespan (specified with the usual <literal>s</literal>,
|
timespan (specified with the usual <literal>s</literal>,
|
||||||
<literal>min</literal>, <literal>h</literal>,
|
<literal>min</literal>, <literal>h</literal>,
|
||||||
<literal>days</literal>, <literal>months</literal>,
|
<literal>days</literal>, <literal>months</literal>,
|
||||||
<literal>weeks</literal>, <literal>years</literal> suffixes),
|
<literal>weeks</literal> and <literal>years</literal> suffixes),
|
||||||
or no more than the specified number of separate journal files
|
or no more than the specified number of separate journal files
|
||||||
remain. Note that running <option>--vacuum-size=</option> has
|
remain. Note that running <option>--vacuum-size=</option> has
|
||||||
only indirect effect on the output shown by
|
only an indirect effect on the output shown by
|
||||||
<option>--disk-usage</option>, as the latter includes active
|
<option>--disk-usage</option>, as the latter includes active
|
||||||
journal files, while the vacuuming operation only operates
|
journal files, while the vacuuming operation only operates
|
||||||
on archived journal files. Similar,
|
on archived journal files. Similarly,
|
||||||
<option>--vacuum-files=</option> might not actually reduce the
|
<option>--vacuum-files=</option> might not actually reduce the
|
||||||
number of journal files to below the specified number, as it
|
number of journal files to below the specified number, as it
|
||||||
will not remove active journal
|
will not remove active journal
|
||||||
|
@ -772,7 +772,7 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><option>--flush</option></term>
|
<term><option>--flush</option></term>
|
||||||
|
|
||||||
<listitem><para>Asks the Journal daemon to flush any log data
|
<listitem><para>Asks the journal daemon to flush any log data
|
||||||
stored in <filename>/run/log/journal</filename> into
|
stored in <filename>/run/log/journal</filename> into
|
||||||
<filename>/var/log/journal</filename>, if persistent storage is
|
<filename>/var/log/journal</filename>, if persistent storage is
|
||||||
enabled. This call does not return until the operation is
|
enabled. This call does not return until the operation is
|
||||||
|
@ -782,7 +782,7 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><option>--rotate</option></term>
|
<term><option>--rotate</option></term>
|
||||||
|
|
||||||
<listitem><para>Asks the Journal daemon to rotate journal files.
|
<listitem><para>Asks the journal daemon to rotate journal files.
|
||||||
</para></listitem>
|
</para></listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
<xi:include href="standard-options.xml" xpointer="help" />
|
<xi:include href="standard-options.xml" xpointer="help" />
|
||||||
|
|
|
@ -203,7 +203,7 @@
|
||||||
|
|
||||||
<para><varname>SystemMaxUse=</varname> and
|
<para><varname>SystemMaxUse=</varname> and
|
||||||
<varname>RuntimeMaxUse=</varname> control how much disk space
|
<varname>RuntimeMaxUse=</varname> control how much disk space
|
||||||
the journal may use up at maximum.
|
the journal may use up at most.
|
||||||
<varname>SystemKeepFree=</varname> and
|
<varname>SystemKeepFree=</varname> and
|
||||||
<varname>RuntimeKeepFree=</varname> control how much disk
|
<varname>RuntimeKeepFree=</varname> control how much disk
|
||||||
space systemd-journald shall leave free for other uses.
|
space systemd-journald shall leave free for other uses.
|
||||||
|
@ -220,12 +220,12 @@
|
||||||
enough free space before and journal files were created, and
|
enough free space before and journal files were created, and
|
||||||
subsequently something else causes the file system to fill up,
|
subsequently something else causes the file system to fill up,
|
||||||
journald will stop using more space, but it will not be
|
journald will stop using more space, but it will not be
|
||||||
removing existing files to reduce footprint again
|
removing existing files to reduce the footprint again,
|
||||||
either.</para>
|
either.</para>
|
||||||
|
|
||||||
<para><varname>SystemMaxFileSize=</varname> and
|
<para><varname>SystemMaxFileSize=</varname> and
|
||||||
<varname>RuntimeMaxFileSize=</varname> control how large
|
<varname>RuntimeMaxFileSize=</varname> control how large
|
||||||
individual journal files may grow at maximum. This influences
|
individual journal files may grow at most. This influences
|
||||||
the granularity in which disk space is made available through
|
the granularity in which disk space is made available through
|
||||||
rotation, i.e. deletion of historic data. Defaults to one
|
rotation, i.e. deletion of historic data. Defaults to one
|
||||||
eighth of the values configured with
|
eighth of the values configured with
|
||||||
|
@ -241,7 +241,7 @@
|
||||||
|
|
||||||
<para><varname>SystemMaxFiles=</varname> and
|
<para><varname>SystemMaxFiles=</varname> and
|
||||||
<varname>RuntimeMaxFiles=</varname> control how many
|
<varname>RuntimeMaxFiles=</varname> control how many
|
||||||
individual journal files to keep at maximum. Note that only
|
individual journal files to keep at most. Note that only
|
||||||
archived files are deleted to reduce the number of files until
|
archived files are deleted to reduce the number of files until
|
||||||
this limit is reached; active files will stay around. This
|
this limit is reached; active files will stay around. This
|
||||||
means that, in effect, there might still be more journal files
|
means that, in effect, there might still be more journal files
|
||||||
|
@ -375,15 +375,15 @@
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
Journal events can be transferred to a different logging daemon
|
Journal events can be transferred to a different logging daemon
|
||||||
in two different ways. In the first method, messages are
|
in two different ways. With the first method, messages are
|
||||||
immediately forwarded to a socket
|
immediately forwarded to a socket
|
||||||
(<filename>/run/systemd/journal/syslog</filename>), where the
|
(<filename>/run/systemd/journal/syslog</filename>), where the
|
||||||
traditional syslog daemon can read them. This method is
|
traditional syslog daemon can read them. This method is
|
||||||
controlled by <varname>ForwardToSyslog=</varname> option. In a
|
controlled by the <varname>ForwardToSyslog=</varname> option. With a
|
||||||
second method, a syslog daemon behaves like a normal journal
|
second method, a syslog daemon behaves like a normal journal
|
||||||
client, and reads messages from the journal files, similarly to
|
client, and reads messages from the journal files, similarly to
|
||||||
<citerefentry><refentrytitle>journalctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
|
<citerefentry><refentrytitle>journalctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
|
||||||
In this method, messages do not have to be read immediately,
|
With this, messages do not have to be read immediately,
|
||||||
which allows a logging daemon which is only started late in boot
|
which allows a logging daemon which is only started late in boot
|
||||||
to access all messages since the start of the system. In
|
to access all messages since the start of the system. In
|
||||||
addition, full structured meta-data is available to it. This
|
addition, full structured meta-data is available to it. This
|
||||||
|
|
|
@ -75,7 +75,7 @@
|
||||||
a udev context. Furthermore, multiple different udev contexts can
|
a udev context. Furthermore, multiple different udev contexts can
|
||||||
be used in parallel by multiple threads. However, a single context
|
be used in parallel by multiple threads. However, a single context
|
||||||
must not be accessed by multiple threads in parallel. The caller
|
must not be accessed by multiple threads in parallel. The caller
|
||||||
is responsible of providing suitable locking if they intend to use
|
is responsible for providing suitable locking if they intend to use
|
||||||
it from multiple threads.</para>
|
it from multiple threads.</para>
|
||||||
|
|
||||||
<para>To introspect a local device on a system, a udev device
|
<para>To introspect a local device on a system, a udev device
|
||||||
|
|
|
@ -255,8 +255,8 @@
|
||||||
|
|
||||||
<listitem><para>Specifies the timeout after system startup or
|
<listitem><para>Specifies the timeout after system startup or
|
||||||
system resume in which systemd will hold off on reacting to
|
system resume in which systemd will hold off on reacting to
|
||||||
LID events. This is required for the system to properly
|
lid events. This is required for the system to properly
|
||||||
detect any hotplugged devices so systemd can ignore LID events
|
detect any hotplugged devices so systemd can ignore lid events
|
||||||
if external monitors, or docks, are connected. If set to 0,
|
if external monitors, or docks, are connected. If set to 0,
|
||||||
systemd will always react immediately, possibly before the
|
systemd will always react immediately, possibly before the
|
||||||
kernel fully probed all hotplugged devices. This is safe, as
|
kernel fully probed all hotplugged devices. This is safe, as
|
||||||
|
|
|
@ -245,7 +245,7 @@
|
||||||
<literal>checksum</literal> and <literal>signature</literal>.
|
<literal>checksum</literal> and <literal>signature</literal>.
|
||||||
If <literal>no</literal>, no verification is done. If
|
If <literal>no</literal>, no verification is done. If
|
||||||
<literal>checksum</literal> is specified, the download is
|
<literal>checksum</literal> is specified, the download is
|
||||||
checked for integrity after transfer is complete, but no
|
checked for integrity after the transfer is complete, but no
|
||||||
signatures are verified. If <literal>signature</literal> is
|
signatures are verified. If <literal>signature</literal> is
|
||||||
specified, the checksum is verified and the images's signature
|
specified, the checksum is verified and the images's signature
|
||||||
is checked against a local keyring of trustable vendors. It is
|
is checked against a local keyring of trustable vendors. It is
|
||||||
|
@ -423,7 +423,7 @@
|
||||||
|
|
||||||
<para>When using the <command>shell</command> command without
|
<para>When using the <command>shell</command> command without
|
||||||
arguments, (thus invoking the executed shell or command on the
|
arguments, (thus invoking the executed shell or command on the
|
||||||
local host), it is similar in many ways to a <citerefentry
|
local host), it is in many ways similar to a <citerefentry
|
||||||
project='die-net'><refentrytitle>su</refentrytitle><manvolnum>1</manvolnum></citerefentry>
|
project='die-net'><refentrytitle>su</refentrytitle><manvolnum>1</manvolnum></citerefentry>
|
||||||
session, but, unlike <command>su</command>, completely isolates
|
session, but, unlike <command>su</command>, completely isolates
|
||||||
the new session from the originating session, so that it
|
the new session from the originating session, so that it
|
||||||
|
@ -433,7 +433,7 @@
|
||||||
environment variables or resource limits, among other
|
environment variables or resource limits, among other
|
||||||
properties.</para>
|
properties.</para>
|
||||||
|
|
||||||
<para>Note that the
|
<para>Note that
|
||||||
<citerefentry><refentrytitle>systemd-run</refentrytitle><manvolnum>1</manvolnum></citerefentry>
|
<citerefentry><refentrytitle>systemd-run</refentrytitle><manvolnum>1</manvolnum></citerefentry>
|
||||||
may be used in place of the <command>shell</command> command,
|
may be used in place of the <command>shell</command> command,
|
||||||
and allows more detailed, low-level configuration of the
|
and allows more detailed, low-level configuration of the
|
||||||
|
@ -633,7 +633,7 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><command>set-limit</command> [<replaceable>NAME</replaceable>] <replaceable>BYTES</replaceable></term>
|
<term><command>set-limit</command> [<replaceable>NAME</replaceable>] <replaceable>BYTES</replaceable></term>
|
||||||
|
|
||||||
<listitem><para>Sets the maximum size in bytes a specific
|
<listitem><para>Sets the maximum size in bytes that a specific
|
||||||
container or VM image, or all images, may grow up to on disk
|
container or VM image, or all images, may grow up to on disk
|
||||||
(disk quota). Takes either one or two parameters. The first,
|
(disk quota). Takes either one or two parameters. The first,
|
||||||
optional parameter refers to a container or VM image name. If
|
optional parameter refers to a container or VM image name. If
|
||||||
|
@ -646,7 +646,7 @@
|
||||||
|
|
||||||
<para>Note that per-container size limits are only supported
|
<para>Note that per-container size limits are only supported
|
||||||
on btrfs file systems. Also note that, if
|
on btrfs file systems. Also note that, if
|
||||||
<command>set-limit</command> is invoked without image
|
<command>set-limit</command> is invoked without an image
|
||||||
parameter, and <filename>/var/lib/machines</filename> is
|
parameter, and <filename>/var/lib/machines</filename> is
|
||||||
empty, and the directory is not located on btrfs, a btrfs
|
empty, and the directory is not located on btrfs, a btrfs
|
||||||
loopback file is implicitly created as
|
loopback file is implicitly created as
|
||||||
|
@ -656,7 +656,7 @@
|
||||||
loopback may later be readjusted with
|
loopback may later be readjusted with
|
||||||
<command>set-limit</command>, as well. If such a
|
<command>set-limit</command>, as well. If such a
|
||||||
loopback-mounted <filename>/var/lib/machines</filename>
|
loopback-mounted <filename>/var/lib/machines</filename>
|
||||||
directory is used, <command>set-limit</command> without image
|
directory is used, <command>set-limit</command> without an image
|
||||||
name alters both the quota setting within the file system as
|
name alters both the quota setting within the file system as
|
||||||
well as the loopback file and file system size
|
well as the loopback file and file system size
|
||||||
itself.</para></listitem>
|
itself.</para></listitem>
|
||||||
|
@ -802,7 +802,7 @@
|
||||||
and places it under the specified name in
|
and places it under the specified name in
|
||||||
<filename>/var/lib/machines/</filename>. When
|
<filename>/var/lib/machines/</filename>. When
|
||||||
<command>import-tar</command> is used, the file specified as
|
<command>import-tar</command> is used, the file specified as
|
||||||
first argument should be a tar archive, possibly compressed
|
the first argument should be a tar archive, possibly compressed
|
||||||
with xz, gzip or bzip2. It will then be unpacked into its own
|
with xz, gzip or bzip2. It will then be unpacked into its own
|
||||||
subvolume in <filename>/var/lib/machines</filename>. When
|
subvolume in <filename>/var/lib/machines</filename>. When
|
||||||
<command>import-raw</command> is used, the file should be a
|
<command>import-raw</command> is used, the file should be a
|
||||||
|
@ -883,17 +883,17 @@
|
||||||
semantics. Specifically, they must consist of one or more
|
semantics. Specifically, they must consist of one or more
|
||||||
non-empty label strings, separated by dots. No leading or trailing
|
non-empty label strings, separated by dots. No leading or trailing
|
||||||
dots are allowed. No sequences of multiple dots are allowed. The
|
dots are allowed. No sequences of multiple dots are allowed. The
|
||||||
label strings may only consists of alphanumeric characters as well
|
label strings may only consist of alphanumeric characters as well
|
||||||
as the dash and underscore. The maximum length of a machine name
|
as the dash and underscore. The maximum length of a machine name
|
||||||
is 64 characters.</para>
|
is 64 characters.</para>
|
||||||
|
|
||||||
<para>A special machine with the name <literal>.host</literal>
|
<para>A special machine with the name <literal>.host</literal>
|
||||||
refers to the running host system itself. This is useful for execution
|
refers to the running host system itself. This is useful for execution
|
||||||
operations or inspecting the host system as well. Not that
|
operations or inspecting the host system as well. Note that
|
||||||
<command>machinectl list</command> will not show this special
|
<command>machinectl list</command> will not show this special
|
||||||
machine unless the <option>--all</option> switch is specified.</para>
|
machine unless the <option>--all</option> switch is specified.</para>
|
||||||
|
|
||||||
<para>Requirements on image names are less strict, however must be
|
<para>Requirements on image names are less strict, however, they must be
|
||||||
valid UTF-8, must be suitable as file names (hence not be the
|
valid UTF-8, must be suitable as file names (hence not be the
|
||||||
single or double dot, and not include a slash), and may not
|
single or double dot, and not include a slash), and may not
|
||||||
contain control characters. Since many operations search for an
|
contain control characters. Since many operations search for an
|
||||||
|
@ -901,7 +901,7 @@
|
||||||
images in the same strict fashion as machines.</para>
|
images in the same strict fashion as machines.</para>
|
||||||
|
|
||||||
<para>A special image with the name <literal>.host</literal>
|
<para>A special image with the name <literal>.host</literal>
|
||||||
refers to the image of the running host system. It is hence
|
refers to the image of the running host system. It hence
|
||||||
conceptually maps to the special <literal>.host</literal> machine
|
conceptually maps to the special <literal>.host</literal> machine
|
||||||
name described above. Note that <command>machinectl
|
name described above. Note that <command>machinectl
|
||||||
list-images</command> won't show this special image either, unless
|
list-images</command> won't show this special image either, unless
|
||||||
|
@ -943,7 +943,7 @@
|
||||||
<listitem><para>A simple directory tree, containing the files
|
<listitem><para>A simple directory tree, containing the files
|
||||||
and directories of the container to boot.</para></listitem>
|
and directories of the container to boot.</para></listitem>
|
||||||
|
|
||||||
<listitem><para>A subvolume (on btrfs file systems), which are
|
<listitem><para>Subvolumes (on btrfs file systems), which are
|
||||||
similar to the simple directories, described above. However,
|
similar to the simple directories, described above. However,
|
||||||
they have additional benefits, such as efficient cloning and
|
they have additional benefits, such as efficient cloning and
|
||||||
quota reporting.</para></listitem>
|
quota reporting.</para></listitem>
|
||||||
|
@ -956,7 +956,7 @@
|
||||||
|
|
||||||
<para>See
|
<para>See
|
||||||
<citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry>
|
<citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry>
|
||||||
for more information on image formats, in particular it's
|
for more information on image formats, in particular its
|
||||||
<option>--directory=</option> and <option>--image=</option>
|
<option>--directory=</option> and <option>--image=</option>
|
||||||
options.</para>
|
options.</para>
|
||||||
</refsect1>
|
</refsect1>
|
||||||
|
@ -1010,8 +1010,8 @@
|
||||||
|
|
||||||
<programlisting># machinectl export-tar fedora myfedora.tar.xz</programlisting>
|
<programlisting># machinectl export-tar fedora myfedora.tar.xz</programlisting>
|
||||||
|
|
||||||
<para>Exports the container <literal>fedora</literal> in an
|
<para>Exports the container <literal>fedora</literal> as an
|
||||||
xz-compress tar file <filename>myfedora.tar.xz</filename> in the
|
xz-compressed tar file <filename>myfedora.tar.xz</filename> into the
|
||||||
current directory.</para>
|
current directory.</para>
|
||||||
</example>
|
</example>
|
||||||
|
|
||||||
|
|
|
@ -129,7 +129,7 @@ IDX LINK TYPE OPERATIONAL SETUP
|
||||||
configured DNS servers, etc.</para>
|
configured DNS servers, etc.</para>
|
||||||
|
|
||||||
<para>When no links are specified, routable links are
|
<para>When no links are specified, routable links are
|
||||||
shown. See also option <option>--all</option>.</para>
|
shown. Also see the option <option>--all</option>.</para>
|
||||||
|
|
||||||
<para>Produces output similar to
|
<para>Produces output similar to
|
||||||
<programlisting>
|
<programlisting>
|
||||||
|
|
|
@ -100,7 +100,7 @@
|
||||||
|
|
||||||
<para>It is recommended to place <literal>myhostname</literal>
|
<para>It is recommended to place <literal>myhostname</literal>
|
||||||
last in the <filename>nsswitch.conf</filename> line to make sure
|
last in the <filename>nsswitch.conf</filename> line to make sure
|
||||||
that this mapping is only used as fallback, and any DNS or
|
that this mapping is only used as fallback, and that any DNS or
|
||||||
<filename>/etc/hosts</filename> based mapping takes
|
<filename>/etc/hosts</filename> based mapping takes
|
||||||
precedence.</para>
|
precedence.</para>
|
||||||
</refsect1>
|
</refsect1>
|
||||||
|
|
|
@ -76,7 +76,7 @@
|
||||||
|
|
||||||
<para>It is recommended to place <literal>mymachines</literal>
|
<para>It is recommended to place <literal>mymachines</literal>
|
||||||
near the end of the <filename>nsswitch.conf</filename> lines to
|
near the end of the <filename>nsswitch.conf</filename> lines to
|
||||||
make sure that its mappings are only used as fallback, and any
|
make sure that its mappings are only used as fallback, and that any
|
||||||
other mappings, such as DNS or <filename>/etc/hosts</filename>
|
other mappings, such as DNS or <filename>/etc/hosts</filename>
|
||||||
based mappings, take precedence.</para>
|
based mappings, take precedence.</para>
|
||||||
</refsect1>
|
</refsect1>
|
||||||
|
|
|
@ -59,7 +59,7 @@
|
||||||
<title>Description</title>
|
<title>Description</title>
|
||||||
|
|
||||||
<para>These configuration files control local DNS and LLMNR
|
<para>These configuration files control local DNS and LLMNR
|
||||||
name resolving.</para>
|
name resolution.</para>
|
||||||
|
|
||||||
</refsect1>
|
</refsect1>
|
||||||
|
|
||||||
|
@ -104,8 +104,8 @@
|
||||||
Resolution support (<ulink
|
Resolution support (<ulink
|
||||||
url="https://tools.ietf.org/html/rfc4795">RFC 4794</ulink>) on
|
url="https://tools.ietf.org/html/rfc4795">RFC 4794</ulink>) on
|
||||||
the local host. If true, enables full LLMNR responder and
|
the local host. If true, enables full LLMNR responder and
|
||||||
resolver support. If false, disable both. If set to
|
resolver support. If false, disables both. If set to
|
||||||
<literal>resolve</literal>, only resolving support is enabled,
|
<literal>resolve</literal>, only resolution support is enabled,
|
||||||
but responding is disabled. Note that
|
but responding is disabled. Note that
|
||||||
<citerefentry><refentrytitle>systemd-networkd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
|
<citerefentry><refentrytitle>systemd-networkd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
|
||||||
also maintains per-interface LLMNR settings. LLMNR will be
|
also maintains per-interface LLMNR settings. LLMNR will be
|
||||||
|
|
|
@ -224,7 +224,7 @@
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><varname>SD_BUS_ERROR_FILE_EXISTS</varname></term>
|
<term><varname>SD_BUS_ERROR_FILE_EXISTS</varname></term>
|
||||||
<listitem><para>The requested file exists already.</para></listitem>
|
<listitem><para>The requested file already exists.</para></listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><varname>SD_BUS_ERROR_UNKNOWN_METHOD</varname></term>
|
<term><varname>SD_BUS_ERROR_UNKNOWN_METHOD</varname></term>
|
||||||
|
|
|
@ -317,7 +317,7 @@
|
||||||
to determine the mask of fields available.</para>
|
to determine the mask of fields available.</para>
|
||||||
|
|
||||||
<para><function>sd_bus_creds_get_pid()</function> will retrieve
|
<para><function>sd_bus_creds_get_pid()</function> will retrieve
|
||||||
the PID (process identifier). Similar,
|
the PID (process identifier). Similarly,
|
||||||
<function>sd_bus_creds_get_ppid()</function> will retrieve the
|
<function>sd_bus_creds_get_ppid()</function> will retrieve the
|
||||||
parent PID. Note that PID 1 has no parent process, in which case
|
parent PID. Note that PID 1 has no parent process, in which case
|
||||||
-ENXIO is returned.</para>
|
-ENXIO is returned.</para>
|
||||||
|
@ -326,14 +326,14 @@
|
||||||
TID (thread identifier).</para>
|
TID (thread identifier).</para>
|
||||||
|
|
||||||
<para><function>sd_bus_creds_get_uid()</function> will retrieve
|
<para><function>sd_bus_creds_get_uid()</function> will retrieve
|
||||||
the numeric UID (user identifier). Similar,
|
the numeric UID (user identifier). Similarly,
|
||||||
<function>sd_bus_creds_get_euid()</function> returns the effective
|
<function>sd_bus_creds_get_euid()</function> returns the effective
|
||||||
UID, <function>sd_bus_creds_get_suid()</function> the saved UID
|
UID, <function>sd_bus_creds_get_suid()</function> the saved UID
|
||||||
and <function>sd_bus_creds_get_fsuid()</function> the file system
|
and <function>sd_bus_creds_get_fsuid()</function> the file system
|
||||||
UID.</para>
|
UID.</para>
|
||||||
|
|
||||||
<para><function>sd_bus_creds_get_gid()</function> will retrieve the
|
<para><function>sd_bus_creds_get_gid()</function> will retrieve the
|
||||||
numeric GID (group identifier). Similar,
|
numeric GID (group identifier). Similarly,
|
||||||
<function>sd_bus_creds_get_egid()</function> returns the effective
|
<function>sd_bus_creds_get_egid()</function> returns the effective
|
||||||
GID, <function>sd_bus_creds_get_sgid()</function> the saved GID
|
GID, <function>sd_bus_creds_get_sgid()</function> the saved GID
|
||||||
and <function>sd_bus_creds_get_fsgid()</function> the file system
|
and <function>sd_bus_creds_get_fsgid()</function> the file system
|
||||||
|
@ -355,7 +355,7 @@
|
||||||
<para><function>sd_bus_creds_get_exe()</function> will retrieve
|
<para><function>sd_bus_creds_get_exe()</function> will retrieve
|
||||||
the path to the program executable (as stored in the
|
the path to the program executable (as stored in the
|
||||||
<filename>/proc/<replaceable>pid</replaceable>/exe</filename>
|
<filename>/proc/<replaceable>pid</replaceable>/exe</filename>
|
||||||
link, but with <literal> (deleted)</literal> suffix removed). Note
|
link, but with the <literal> (deleted)</literal> suffix removed). Note
|
||||||
that kernel threads do not have an executable path, in which case
|
that kernel threads do not have an executable path, in which case
|
||||||
-ENXIO is returned.</para>
|
-ENXIO is returned.</para>
|
||||||
|
|
||||||
|
@ -372,36 +372,36 @@
|
||||||
|
|
||||||
<para><function>sd_bus_creds_get_unit()</function> will retrieve
|
<para><function>sd_bus_creds_get_unit()</function> will retrieve
|
||||||
the systemd unit name (in the system instance of systemd) that the
|
the systemd unit name (in the system instance of systemd) that the
|
||||||
process is part of. See
|
process is a part of. See
|
||||||
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>. For
|
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>. For
|
||||||
processes that are not part of a unit, returns -ENXIO.
|
processes that are not part of a unit, returns -ENXIO.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para><function>sd_bus_creds_get_user_unit()</function> will
|
<para><function>sd_bus_creds_get_user_unit()</function> will
|
||||||
retrieve the systemd unit name (in the user instance of systemd)
|
retrieve the systemd unit name (in the user instance of systemd)
|
||||||
that the process is part of. See
|
that the process is a part of. See
|
||||||
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>. For
|
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>. For
|
||||||
processes that are not part of a user unit, returns -ENXIO.
|
processes that are not part of a user unit, returns -ENXIO.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para><function>sd_bus_creds_get_slice()</function> will retrieve
|
<para><function>sd_bus_creds_get_slice()</function> will retrieve
|
||||||
the systemd slice (a unit in the system instance of systemd) that
|
the systemd slice (a unit in the system instance of systemd) that
|
||||||
the process is part of. See
|
the process is a part of. See
|
||||||
<citerefentry><refentrytitle>systemd.slice</refentrytitle><manvolnum>5</manvolnum></citerefentry>. Similar,
|
<citerefentry><refentrytitle>systemd.slice</refentrytitle><manvolnum>5</manvolnum></citerefentry>. Similarly,
|
||||||
<function>sd_bus_creds_get_user_slice()</function> retrieves the
|
<function>sd_bus_creds_get_user_slice()</function> retrieves the
|
||||||
systemd slice of the process, in the user instance of systemd.
|
systemd slice of the process, in the user instance of systemd.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para><function>sd_bus_creds_get_session()</function> will
|
<para><function>sd_bus_creds_get_session()</function> will
|
||||||
retrieve the identifier of the login session that the process is
|
retrieve the identifier of the login session that the process is
|
||||||
part of. See
|
a part of. See
|
||||||
<citerefentry><refentrytitle>systemd-logind.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>. For
|
<citerefentry><refentrytitle>systemd-logind.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>. For
|
||||||
processes that are not part of a session, returns -ENXIO.
|
processes that are not part of a session, returns -ENXIO.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para><function>sd_bus_creds_get_owner_uid()</function> will
|
<para><function>sd_bus_creds_get_owner_uid()</function> will
|
||||||
retrieve the numeric UID (user identifier) of the user who owns
|
retrieve the numeric UID (user identifier) of the user who owns
|
||||||
the login session that the process is part of. See
|
the login session that the process is a part of. See
|
||||||
<citerefentry><refentrytitle>systemd-logind.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
|
<citerefentry><refentrytitle>systemd-logind.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
|
||||||
For processes that are not part of a session, returns -ENXIO.
|
For processes that are not part of a session, returns -ENXIO.
|
||||||
</para>
|
</para>
|
||||||
|
@ -494,7 +494,7 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><constant>-ENODATA</constant></term>
|
<term><constant>-ENODATA</constant></term>
|
||||||
|
|
||||||
<listitem><para>Given field is not available in the
|
<listitem><para>The given field is not available in the
|
||||||
credentials object <parameter>c</parameter>.</para>
|
credentials object <parameter>c</parameter>.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
@ -502,7 +502,7 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><constant>-ENXIO</constant></term>
|
<term><constant>-ENXIO</constant></term>
|
||||||
|
|
||||||
<listitem><para>Given field is not specified for the described
|
<listitem><para>The given field is not specified for the described
|
||||||
process or peer. This will be returned by
|
process or peer. This will be returned by
|
||||||
<function>sd_bus_get_unit()</function>,
|
<function>sd_bus_get_unit()</function>,
|
||||||
<function>sd_bus_get_slice()</function>,
|
<function>sd_bus_get_slice()</function>,
|
||||||
|
@ -514,8 +514,8 @@
|
||||||
slice, or logind session. It will also be returned by
|
slice, or logind session. It will also be returned by
|
||||||
<function>sd_bus_creds_get_exe()</function> and
|
<function>sd_bus_creds_get_exe()</function> and
|
||||||
<function>sd_bus_creds_get_cmdline()</function> for kernel
|
<function>sd_bus_creds_get_cmdline()</function> for kernel
|
||||||
threads (since these aren't started from an executable binary
|
threads (since these are not started from an executable binary,
|
||||||
or have a command line),
|
nor have a command line), and by
|
||||||
<function>sd_bus_creds_get_audit_session_id()</function> and
|
<function>sd_bus_creds_get_audit_session_id()</function> and
|
||||||
<function>sd_bus_creds_get_audit_login_uid()</function> when
|
<function>sd_bus_creds_get_audit_login_uid()</function> when
|
||||||
the process is not part of an audit session, and
|
the process is not part of an audit session, and
|
||||||
|
|
|
@ -130,7 +130,7 @@
|
||||||
<para><function>sd_bus_creds_new_from_pid()</function> creates a
|
<para><function>sd_bus_creds_new_from_pid()</function> creates a
|
||||||
new credentials object and fills it with information about the
|
new credentials object and fills it with information about the
|
||||||
process <parameter>pid</parameter>. The pointer to this object
|
process <parameter>pid</parameter>. The pointer to this object
|
||||||
will be stored in <parameter>ret</parameter> pointer. Note that
|
will be stored in the <parameter>ret</parameter> pointer. Note that
|
||||||
credential objects may also be created and retrieved via
|
credential objects may also be created and retrieved via
|
||||||
<citerefentry><refentrytitle>sd_bus_get_name_creds</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
<citerefentry><refentrytitle>sd_bus_get_name_creds</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
||||||
<citerefentry><refentrytitle>sd_bus_get_owner_creds</refentrytitle><manvolnum>3</manvolnum></citerefentry>
|
<citerefentry><refentrytitle>sd_bus_get_owner_creds</refentrytitle><manvolnum>3</manvolnum></citerefentry>
|
||||||
|
@ -171,11 +171,11 @@
|
||||||
<constant>SD_BUS_CREDS_AUDIT_LOGIN_UID</constant>,
|
<constant>SD_BUS_CREDS_AUDIT_LOGIN_UID</constant>,
|
||||||
<constant>SD_BUS_CREDS_TTY</constant>,
|
<constant>SD_BUS_CREDS_TTY</constant>,
|
||||||
<constant>SD_BUS_CREDS_UNIQUE_NAME</constant>,
|
<constant>SD_BUS_CREDS_UNIQUE_NAME</constant>,
|
||||||
<constant>SD_BUS_CREDS_WELL_KNOWN_NAMES</constant>,
|
<constant>SD_BUS_CREDS_WELL_KNOWN_NAMES</constant>, and
|
||||||
<constant>SD_BUS_CREDS_DESCRIPTION</constant>. Use the special
|
<constant>SD_BUS_CREDS_DESCRIPTION</constant>. Use the special
|
||||||
value <constant>_SD_BUS_CREDS_ALL</constant> to request all
|
value <constant>_SD_BUS_CREDS_ALL</constant> to request all
|
||||||
supported fields. The <constant>SD_BUS_CREDS_AUGMENT</constant>
|
supported fields. The <constant>SD_BUS_CREDS_AUGMENT</constant>
|
||||||
may not be ORed into the mask for invocations of
|
constant may not be ORed into the mask for invocations of
|
||||||
<function>sd_bus_creds_new_from_pid()</function>.</para>
|
<function>sd_bus_creds_new_from_pid()</function>.</para>
|
||||||
|
|
||||||
<para>Fields can be retrieved from the credentials object using
|
<para>Fields can be retrieved from the credentials object using
|
||||||
|
@ -204,14 +204,14 @@
|
||||||
for the credential fields that could not be determined atomically
|
for the credential fields that could not be determined atomically
|
||||||
at peer connection time, and which were later added by reading
|
at peer connection time, and which were later added by reading
|
||||||
augmenting credential data from
|
augmenting credential data from
|
||||||
<filename>/proc</filename>. Similar, for credential objects
|
<filename>/proc</filename>. Similarly, for credential objects
|
||||||
retrieved via <function>sd_bus_get_owner_creds()</function>, the
|
retrieved via <function>sd_bus_get_owner_creds()</function>, the
|
||||||
mask is set for the fields that could not be determined atomically
|
mask is set for the fields that could not be determined atomically
|
||||||
at bus creation time, but have been augmented. Similar, for
|
at bus creation time, but have been augmented. Similarly, for
|
||||||
credential objects retrieved via
|
credential objects retrieved via
|
||||||
<function>sd_bus_message_get_creds()</function>, the mask is set
|
<function>sd_bus_message_get_creds()</function>, the mask is set
|
||||||
for the fields that could not be determined atomically at message
|
for the fields that could not be determined atomically at message
|
||||||
send time, but have been augmented. The mask returned by
|
sending time, but have been augmented. The mask returned by
|
||||||
<function>sd_bus_creds_get_augmented_mask()</function> is always a
|
<function>sd_bus_creds_get_augmented_mask()</function> is always a
|
||||||
subset of (or identical to) the mask returned by
|
subset of (or identical to) the mask returned by
|
||||||
<function>sd_bus_creds_get_mask()</function> for the same
|
<function>sd_bus_creds_get_mask()</function> for the same
|
||||||
|
|
|
@ -120,8 +120,8 @@
|
||||||
call), the connection is terminated. Note that the connection is
|
call), the connection is terminated. Note that the connection is
|
||||||
not automatically terminated when the associated thread ends. It
|
not automatically terminated when the associated thread ends. It
|
||||||
is important to drop the last reference to the bus connection
|
is important to drop the last reference to the bus connection
|
||||||
explicitly before the thread ends, or otherwise, the connection will
|
explicitly before the thread ends, as otherwise, the connection will
|
||||||
be leaked. Also, queued but unread or unwritten messages keep the
|
leak. Also, queued but unread or unwritten messages keep the
|
||||||
bus referenced, see below.</para>
|
bus referenced, see below.</para>
|
||||||
|
|
||||||
<para><function>sd_bus_default_user()</function> returns a user
|
<para><function>sd_bus_default_user()</function> returns a user
|
||||||
|
@ -139,14 +139,14 @@
|
||||||
<function>sd_bus_open_system()</function> does the same, but
|
<function>sd_bus_open_system()</function> does the same, but
|
||||||
connects to the system bus. In contrast to
|
connects to the system bus. In contrast to
|
||||||
<function>sd_bus_default()</function>,
|
<function>sd_bus_default()</function>,
|
||||||
<function>sd_bus_default_user()</function>,
|
<function>sd_bus_default_user()</function>, and
|
||||||
<function>sd_bus_default_system()</function>, these calls return
|
<function>sd_bus_default_system()</function>, these calls return
|
||||||
new, independent connection objects that are not associated with
|
new, independent connection objects that are not associated with
|
||||||
the invoking thread and are not shared between multiple
|
the invoking thread and are not shared between multiple
|
||||||
invocations. It is recommended to share connections per thread to
|
invocations. It is recommended to share connections per thread to
|
||||||
efficiently make use the available resources. Thus, it is
|
efficiently make use the available resources. Thus, it is
|
||||||
recommended to use <function>sd_bus_default()</function>,
|
recommended to use <function>sd_bus_default()</function>,
|
||||||
<function>sd_bus_default_user()</function>,
|
<function>sd_bus_default_user()</function> and
|
||||||
<function>sd_bus_default_system()</function> to connect to the
|
<function>sd_bus_default_system()</function> to connect to the
|
||||||
user or system buses.</para>
|
user or system buses.</para>
|
||||||
|
|
||||||
|
|
|
@ -200,7 +200,7 @@
|
||||||
call can fail if no memory may be allocated for the name and
|
call can fail if no memory may be allocated for the name and
|
||||||
message strings, in which case an
|
message strings, in which case an
|
||||||
<constant>SD_BUS_ERROR_NO_MEMORY</constant> error might be set
|
<constant>SD_BUS_ERROR_NO_MEMORY</constant> error might be set
|
||||||
instead and -ENOMEM returned. Do not use this call on error
|
instead and -ENOMEM be returned. Do not use this call on error
|
||||||
structures that are already initialized. If you intend to reuse an
|
structures that are already initialized. If you intend to reuse an
|
||||||
error structure, free the old data stored in it with
|
error structure, free the old data stored in it with
|
||||||
<function>sd_bus_error_free()</function> first.</para>
|
<function>sd_bus_error_free()</function> first.</para>
|
||||||
|
@ -238,7 +238,7 @@
|
||||||
convenient usage in <function>return</function> statements. This
|
convenient usage in <function>return</function> statements. This
|
||||||
call might fail due to lack of memory, in which case an
|
call might fail due to lack of memory, in which case an
|
||||||
<constant>SD_BUS_ERROR_NO_MEMORY</constant> error is set instead,
|
<constant>SD_BUS_ERROR_NO_MEMORY</constant> error is set instead,
|
||||||
and -ENOMEM returned.</para>
|
and -ENOMEM is returned.</para>
|
||||||
|
|
||||||
<para><function>sd_bus_error_set_errnof()</function> is similar to
|
<para><function>sd_bus_error_set_errnof()</function> is similar to
|
||||||
<function>sd_bus_error_set_errno()</function>, but in addition to
|
<function>sd_bus_error_set_errno()</function>, but in addition to
|
||||||
|
@ -295,10 +295,10 @@
|
||||||
<title>Return Value</title>
|
<title>Return Value</title>
|
||||||
|
|
||||||
<para>The functions <function>sd_bus_error_set()</function>,
|
<para>The functions <function>sd_bus_error_set()</function>,
|
||||||
<function>sd_bus_error_setf()</function>,
|
<function>sd_bus_error_setf()</function>, and
|
||||||
<function>sd_bus_error_set_const()</function>, when successful,
|
<function>sd_bus_error_set_const()</function>, when successful,
|
||||||
return the negative errno value corresponding to the
|
return the negative errno value corresponding to the
|
||||||
<parameter>name</parameter> parameter. Functions
|
<parameter>name</parameter> parameter. The functions
|
||||||
<function>sd_bus_error_set_errno()</function>,
|
<function>sd_bus_error_set_errno()</function>,
|
||||||
<function>sd_bus_error_set_errnof()</function> and
|
<function>sd_bus_error_set_errnof()</function> and
|
||||||
<function>sd_bus_error_set_errnofv()</function>, when successful,
|
<function>sd_bus_error_set_errnofv()</function>, when successful,
|
||||||
|
|
|
@ -95,7 +95,7 @@
|
||||||
<para>The function takes a pointer to an array of
|
<para>The function takes a pointer to an array of
|
||||||
<structname>sd_bus_error_map</structname> structures. A reference
|
<structname>sd_bus_error_map</structname> structures. A reference
|
||||||
to the specified array is added to the lookup tables for error
|
to the specified array is added to the lookup tables for error
|
||||||
mappings. Note that the structure is not copied, it is hence
|
mappings. Note that the structure is not copied, and that it is hence
|
||||||
essential that the array stays available and constant during the
|
essential that the array stays available and constant during the
|
||||||
entire remaining runtime of the process.</para>
|
entire remaining runtime of the process.</para>
|
||||||
|
|
||||||
|
|
|
@ -132,7 +132,7 @@
|
||||||
the offset is specified as zero and the size specified as
|
the offset is specified as zero and the size specified as
|
||||||
UINT64_MAX the full memory file descriptor contents is used. The
|
UINT64_MAX the full memory file descriptor contents is used. The
|
||||||
memory file descriptor is sealed by this call if it hasn't been
|
memory file descriptor is sealed by this call if it hasn't been
|
||||||
sealed yet, and cannot be modified a after this call. See
|
sealed yet, and cannot be modified after this call. See
|
||||||
<citerefentry
|
<citerefentry
|
||||||
project='man-pages'><refentrytitle>memfd_create</refentrytitle><manvolnum>2</manvolnum></citerefentry>
|
project='man-pages'><refentrytitle>memfd_create</refentrytitle><manvolnum>2</manvolnum></citerefentry>
|
||||||
for details about memory file descriptors. Appending arrays with
|
for details about memory file descriptors. Appending arrays with
|
||||||
|
@ -171,7 +171,7 @@
|
||||||
copying items to the message, it returns a pointer to the
|
copying items to the message, it returns a pointer to the
|
||||||
destination area to the caller in pointer
|
destination area to the caller in pointer
|
||||||
<parameter>p</parameter>. The caller should subsequently write the
|
<parameter>p</parameter>. The caller should subsequently write the
|
||||||
array contents to this memory. Modifications of the memory
|
array contents to this memory. Modifications to the memory
|
||||||
pointed to should only occur until the next operation on the bus
|
pointed to should only occur until the next operation on the bus
|
||||||
message is invoked. Most importantly, the memory should not be
|
message is invoked. Most importantly, the memory should not be
|
||||||
altered anymore when another field has been added to the message
|
altered anymore when another field has been added to the message
|
||||||
|
|
|
@ -83,7 +83,7 @@
|
||||||
<citerefentry><refentrytitle>clock_gettime</refentrytitle><manvolnum>2</manvolnum></citerefentry>
|
<citerefentry><refentrytitle>clock_gettime</refentrytitle><manvolnum>2</manvolnum></citerefentry>
|
||||||
for details.</para>
|
for details.</para>
|
||||||
|
|
||||||
<para>Similar,
|
<para>Similarly,
|
||||||
<function>sd_bus_message_get_realtime_usec()</function> returns
|
<function>sd_bus_message_get_realtime_usec()</function> returns
|
||||||
the realtime (wallclock) timestamp of the time the message was
|
the realtime (wallclock) timestamp of the time the message was
|
||||||
sent. This value is in microseconds since Jan 1st, 1970, i.e. in
|
sent. This value is in microseconds since Jan 1st, 1970, i.e. in
|
||||||
|
|
|
@ -118,7 +118,7 @@
|
||||||
|
|
||||||
<para><function>sd_bus_negotiate_creds()</function> controls
|
<para><function>sd_bus_negotiate_creds()</function> controls
|
||||||
whether and which implicit sender credentials shall be attached
|
whether and which implicit sender credentials shall be attached
|
||||||
automatically to all incoming messages. Takes a bus object, a
|
automatically to all incoming messages. Takes a bus object and a
|
||||||
boolean indicating whether to enable or disable the credential
|
boolean indicating whether to enable or disable the credential
|
||||||
parts encoded in the bit mask value argument. Note that not all
|
parts encoded in the bit mask value argument. Note that not all
|
||||||
transports support attaching sender credentials to messages, or do
|
transports support attaching sender credentials to messages, or do
|
||||||
|
@ -143,7 +143,7 @@
|
||||||
after a connection has been set up. Note that, when operating on a
|
after a connection has been set up. Note that, when operating on a
|
||||||
connection that is shared between multiple components of the same
|
connection that is shared between multiple components of the same
|
||||||
program (for example via
|
program (for example via
|
||||||
<citerefentry><refentrytitle>sd_bus_default</refentrytitle><manvolnum>3</manvolnum></citerefentry>)
|
<citerefentry><refentrytitle>sd_bus_default</refentrytitle><manvolnum>3</manvolnum></citerefentry>),
|
||||||
it is highly recommended to only enable additional per message
|
it is highly recommended to only enable additional per message
|
||||||
metadata fields, but never disable them again, in order not to
|
metadata fields, but never disable them again, in order not to
|
||||||
disable functionality needed by other components.</para>
|
disable functionality needed by other components.</para>
|
||||||
|
|
|
@ -144,7 +144,7 @@
|
||||||
(<literal>char **</literal>) via varargs. The decoded label
|
(<literal>char **</literal>) via varargs. The decoded label
|
||||||
will be stored there. Each <literal>%</literal> character will
|
will be stored there. Each <literal>%</literal> character will
|
||||||
only match the current label. It will never match across labels.
|
only match the current label. It will never match across labels.
|
||||||
Furthermore, only a single such directive is allowed per label.
|
Furthermore, only a single directive is allowed per label.
|
||||||
If <literal>NULL</literal> is passed as output storage, the
|
If <literal>NULL</literal> is passed as output storage, the
|
||||||
label is verified but not returned to the caller.</para>
|
label is verified but not returned to the caller.</para>
|
||||||
</refsect1>
|
</refsect1>
|
||||||
|
|
|
@ -157,7 +157,7 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><constant>-EBUSY</constant></term>
|
<term><constant>-EBUSY</constant></term>
|
||||||
|
|
||||||
<listitem><para>An handler is already installed for this
|
<listitem><para>A handler is already installed for this
|
||||||
child.</para></listitem>
|
child.</para></listitem>
|
||||||
|
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
|
@ -90,7 +90,7 @@
|
||||||
<refsect1>
|
<refsect1>
|
||||||
<title>Description</title>
|
<title>Description</title>
|
||||||
|
|
||||||
<para>Those three functions add new event sources to an event loop
|
<para>These three functions add new event sources to an event loop
|
||||||
object. The event loop is specified in
|
object. The event loop is specified in
|
||||||
<parameter>event</parameter>, the event source is returned in the
|
<parameter>event</parameter>, the event source is returned in the
|
||||||
<parameter>source</parameter> parameter. The event sources are
|
<parameter>source</parameter> parameter. The event sources are
|
||||||
|
|
|
@ -82,7 +82,7 @@
|
||||||
|
|
||||||
<para><function>sd_event_add_signal()</function> adds a new signal
|
<para><function>sd_event_add_signal()</function> adds a new signal
|
||||||
event source to an event loop object. The event loop is specified
|
event source to an event loop object. The event loop is specified
|
||||||
in <parameter>event</parameter>, the event source is returned in
|
in <parameter>event</parameter>, and the event source is returned in
|
||||||
the <parameter>source</parameter> parameter. The
|
the <parameter>source</parameter> parameter. The
|
||||||
<parameter>signal</parameter> parameter specifies the signal to be handled
|
<parameter>signal</parameter> parameter specifies the signal to be handled
|
||||||
(see
|
(see
|
||||||
|
@ -149,7 +149,7 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><constant>-EBUSY</constant></term>
|
<term><constant>-EBUSY</constant></term>
|
||||||
|
|
||||||
<listitem><para>An handler is already installed for this
|
<listitem><para>A handler is already installed for this
|
||||||
signal or the signal was not blocked previously.</para></listitem>
|
signal or the signal was not blocked previously.</para></listitem>
|
||||||
|
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
|
@ -46,7 +46,7 @@
|
||||||
<refname>sd_event_run</refname>
|
<refname>sd_event_run</refname>
|
||||||
<refname>sd_event_loop</refname>
|
<refname>sd_event_loop</refname>
|
||||||
|
|
||||||
<refpurpose>Run libsystemd event loop</refpurpose>
|
<refpurpose>Run the libsystemd event loop</refpurpose>
|
||||||
</refnamediv>
|
</refnamediv>
|
||||||
|
|
||||||
<refsynopsisdiv>
|
<refsynopsisdiv>
|
||||||
|
@ -72,7 +72,7 @@
|
||||||
<para><function>sd_event_run()</function> can be used to run one
|
<para><function>sd_event_run()</function> can be used to run one
|
||||||
iteration of the event loop of libsystemd. This function waits
|
iteration of the event loop of libsystemd. This function waits
|
||||||
until an event to process is available, and dispatches a handler
|
until an event to process is available, and dispatches a handler
|
||||||
for it. Parameter <parameter>timeout</parameter> specifices the
|
for it. The <parameter>timeout</parameter> parameter specifices the
|
||||||
maximum time (in microseconds) to wait. <constant>(uint64_t)
|
maximum time (in microseconds) to wait. <constant>(uint64_t)
|
||||||
-1</constant> may be used to specify an infinite timeout.</para>
|
-1</constant> may be used to specify an infinite timeout.</para>
|
||||||
|
|
||||||
|
@ -121,7 +121,7 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><constant>-EINVAL</constant></term>
|
<term><constant>-EINVAL</constant></term>
|
||||||
|
|
||||||
<listitem><para>Parameter <parameter>event</parameter> is
|
<listitem><para>The <parameter>event</parameter> parameter is
|
||||||
<constant>NULL</constant>.</para></listitem>
|
<constant>NULL</constant>.</para></listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
|
@ -176,7 +176,7 @@
|
||||||
<citerefentry><refentrytitle>sd_event_add_defer</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
<citerefentry><refentrytitle>sd_event_add_defer</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
||||||
<citerefentry><refentrytitle>sd_event_add_exit</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
<citerefentry><refentrytitle>sd_event_add_exit</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
||||||
<citerefentry><refentrytitle>sd_event_add_post</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
<citerefentry><refentrytitle>sd_event_add_post</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
||||||
<ulink url="https://developer.gnome.org/glib/unstable/glib-The-Main-Event-Loop.html">GLIb Main Event Loop</ulink>.
|
<ulink url="https://developer.gnome.org/glib/unstable/glib-The-Main-Event-Loop.html">GLib Main Event Loop</ulink>.
|
||||||
</para>
|
</para>
|
||||||
</refsect1>
|
</refsect1>
|
||||||
|
|
||||||
|
|
|
@ -77,7 +77,7 @@
|
||||||
<parameter>source</parameter>. This name will be used in error
|
<parameter>source</parameter>. This name will be used in error
|
||||||
messages generated by
|
messages generated by
|
||||||
<citerefentry><refentrytitle>sd-event</refentrytitle><manvolnum>3</manvolnum></citerefentry>
|
<citerefentry><refentrytitle>sd-event</refentrytitle><manvolnum>3</manvolnum></citerefentry>
|
||||||
for this source. Specified <parameter>name</parameter> must point
|
for this source. The <parameter>name</parameter> must point
|
||||||
to a <constant>NUL</constant>-terminated string or be
|
to a <constant>NUL</constant>-terminated string or be
|
||||||
<constant>NULL</constant>. In the latter case, the name will be
|
<constant>NULL</constant>. In the latter case, the name will be
|
||||||
unset. The string is copied internally, so the
|
unset. The string is copied internally, so the
|
||||||
|
@ -128,7 +128,7 @@
|
||||||
<refsect1>
|
<refsect1>
|
||||||
<title>Notes</title>
|
<title>Notes</title>
|
||||||
|
|
||||||
<para>Functions described here are available as a
|
<para>The functions described here are available as a
|
||||||
shared library, which can be compiled and linked to with the
|
shared library, which can be compiled and linked to with the
|
||||||
<constant>libsystemd</constant> <citerefentry
|
<constant>libsystemd</constant> <citerefentry
|
||||||
project='die-net'><refentrytitle>pkg-config</refentrytitle><manvolnum>1</manvolnum></citerefentry>
|
project='die-net'><refentrytitle>pkg-config</refentrytitle><manvolnum>1</manvolnum></citerefentry>
|
||||||
|
|
|
@ -47,7 +47,7 @@
|
||||||
<refname>sd_event_prepare</refname>
|
<refname>sd_event_prepare</refname>
|
||||||
<refname>sd_event_dispatch</refname>
|
<refname>sd_event_dispatch</refname>
|
||||||
|
|
||||||
<refpurpose>Run parts of libsystemd event loop</refpurpose>
|
<refpurpose>Run parts of the libsystemd event loop</refpurpose>
|
||||||
</refnamediv>
|
</refnamediv>
|
||||||
|
|
||||||
<refsynopsisdiv>
|
<refsynopsisdiv>
|
||||||
|
@ -123,8 +123,8 @@
|
||||||
└──────────┘
|
└──────────┘
|
||||||
</programlisting>
|
</programlisting>
|
||||||
|
|
||||||
<para>All three functions as the first argument take the event
|
<para>All three functions take, as the first argument, the event
|
||||||
loop object <parameter>event</parameter> that is created with with
|
loop object <parameter>event</parameter> that is created with
|
||||||
<function>sd_event_new</function>. The timeout for
|
<function>sd_event_new</function>. The timeout for
|
||||||
<function>sd_event_wait</function> is specified with
|
<function>sd_event_wait</function> is specified with
|
||||||
<parameter>timeout</parameter> in milliseconds.
|
<parameter>timeout</parameter> in milliseconds.
|
||||||
|
@ -155,7 +155,7 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><constant>-EINVAL</constant></term>
|
<term><constant>-EINVAL</constant></term>
|
||||||
|
|
||||||
<listitem><para>Parameter <parameter>event</parameter> is
|
<listitem><para>The <parameter>event</parameter> parameter is
|
||||||
<constant>NULL</constant>.</para></listitem>
|
<constant>NULL</constant>.</para></listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
|
|
|
@ -145,7 +145,7 @@
|
||||||
<function>sd_is_socket()</function> and related calls is not
|
<function>sd_is_socket()</function> and related calls is not
|
||||||
sufficient. Note that the names used are not unique in any
|
sufficient. Note that the names used are not unique in any
|
||||||
way. The returned array of strings has as many entries as file
|
way. The returned array of strings has as many entries as file
|
||||||
descriptors has been received, plus a final NULL pointer
|
descriptors have been received, plus a final NULL pointer
|
||||||
terminating the array. The caller needs to free the array itself
|
terminating the array. The caller needs to free the array itself
|
||||||
and each of its elements with libc's <function>free()</function>
|
and each of its elements with libc's <function>free()</function>
|
||||||
call after use. If the <parameter>names</parameter> parameter is
|
call after use. If the <parameter>names</parameter> parameter is
|
||||||
|
|
|
@ -244,7 +244,7 @@
|
||||||
different names to submitted file descriptors, submit them in
|
different names to submitted file descriptors, submit them in
|
||||||
seperate invocations of
|
seperate invocations of
|
||||||
<function>sd_pid_notify_with_fds()</function>. The name may
|
<function>sd_pid_notify_with_fds()</function>. The name may
|
||||||
consist of any ASCII characters, but must not contain control
|
consist of any ASCII character, but must not contain control
|
||||||
characters or <literal>:</literal>. It may not be longer than
|
characters or <literal>:</literal>. It may not be longer than
|
||||||
255 characters. If a submitted name does not follow these
|
255 characters. If a submitted name does not follow these
|
||||||
restrictions, it is ignored.</para></listitem>
|
restrictions, it is ignored.</para></listitem>
|
||||||
|
|
|
@ -205,7 +205,7 @@
|
||||||
determine the Unix UID (user identifier) of the owner of the
|
determine the Unix UID (user identifier) of the owner of the
|
||||||
session of a process identified the specified PID. Note that this
|
session of a process identified the specified PID. Note that this
|
||||||
function will succeed for user processes which are shared between
|
function will succeed for user processes which are shared between
|
||||||
multiple login sessions of the same user, where
|
multiple login sessions of the same user, whereas
|
||||||
<function>sd_pid_get_session()</function> will fail. For processes
|
<function>sd_pid_get_session()</function> will fail. For processes
|
||||||
not being part of a login session and not being a shared process
|
not being part of a login session and not being a shared process
|
||||||
of a user, this function will fail with -ENODATA.</para>
|
of a user, this function will fail with -ENODATA.</para>
|
||||||
|
@ -227,7 +227,7 @@
|
||||||
<citerefentry project='man-pages'><refentrytitle>free</refentrytitle><manvolnum>3</manvolnum></citerefentry>
|
<citerefentry project='man-pages'><refentrytitle>free</refentrytitle><manvolnum>3</manvolnum></citerefentry>
|
||||||
call after use.</para>
|
call after use.</para>
|
||||||
|
|
||||||
<para>Similar, <function>sd_pid_get_user_slice()</function>
|
<para>Similarly, <function>sd_pid_get_user_slice()</function>
|
||||||
returns the user slice (as managed by the user's systemd instance)
|
returns the user slice (as managed by the user's systemd instance)
|
||||||
of a process.</para>
|
of a process.</para>
|
||||||
|
|
||||||
|
@ -294,7 +294,7 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><constant>-ENODATA</constant></term>
|
<term><constant>-ENODATA</constant></term>
|
||||||
|
|
||||||
<listitem><para>Given field is not specified for the described
|
<listitem><para>The given field is not specified for the described
|
||||||
process or peer.</para>
|
process or peer.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
|
@ -158,7 +158,7 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><constant>-ENODATA</constant></term>
|
<term><constant>-ENODATA</constant></term>
|
||||||
|
|
||||||
<listitem><para>Given field is not specified for the described
|
<listitem><para>The given field is not specified for the described
|
||||||
seat.</para>
|
seat.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
|
@ -306,7 +306,7 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><constant>-ENODATA</constant></term>
|
<term><constant>-ENODATA</constant></term>
|
||||||
|
|
||||||
<listitem><para>Given field is not specified for the described
|
<listitem><para>The given field is not specified for the described
|
||||||
session.</para>
|
session.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
|
@ -179,7 +179,7 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><constant>-ENODATA</constant></term>
|
<term><constant>-ENODATA</constant></term>
|
||||||
|
|
||||||
<listitem><para>Given field is not specified for the described
|
<listitem><para>The given field is not specified for the described
|
||||||
user.</para>
|
user.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
|
@ -38,7 +38,7 @@
|
||||||
<refsection id='main-conf'>
|
<refsection id='main-conf'>
|
||||||
<title>Configuration Directories and Precedence</title>
|
<title>Configuration Directories and Precedence</title>
|
||||||
|
|
||||||
<para>Default configuration is defined during compilation, so a
|
<para>The default configuration is defined during compilation, so a
|
||||||
configuration file is only needed when it is necessary to deviate
|
configuration file is only needed when it is necessary to deviate
|
||||||
from those defaults. By default, the configuration file in
|
from those defaults. By default, the configuration file in
|
||||||
<filename>/etc/systemd/</filename> contains commented out entries
|
<filename>/etc/systemd/</filename> contains commented out entries
|
||||||
|
|
|
@ -142,8 +142,8 @@ net.bridge.bridge-nf-call-arptables = 0
|
||||||
<para>This method applies settings when the module is
|
<para>This method applies settings when the module is
|
||||||
loaded. Please note that, unless the <filename>br_netfilter</filename>
|
loaded. Please note that, unless the <filename>br_netfilter</filename>
|
||||||
module is loaded, bridged packets will not be filtered by
|
module is loaded, bridged packets will not be filtered by
|
||||||
netfilter (starting with kernel 3.18), so simply not loading the
|
Netfilter (starting with kernel 3.18), so simply not loading the
|
||||||
module is suffient to avoid filtering.</para>
|
module is sufficient to avoid filtering.</para>
|
||||||
</example>
|
</example>
|
||||||
|
|
||||||
<example>
|
<example>
|
||||||
|
@ -163,9 +163,9 @@ net.bridge.bridge-nf-call-arptables = 0
|
||||||
|
|
||||||
<para>This method forces the module to be always loaded. Please
|
<para>This method forces the module to be always loaded. Please
|
||||||
note that, unless the <filename>br_netfilter</filename> module is
|
note that, unless the <filename>br_netfilter</filename> module is
|
||||||
loaded, bridged packets will not be filtered with netfilter
|
loaded, bridged packets will not be filtered with Netfilter
|
||||||
(starting with kernel 3.18), so simply not loading the module is
|
(starting with kernel 3.18), so simply not loading the module is
|
||||||
suffient to avoid filtering.</para>
|
sufficient to avoid filtering.</para>
|
||||||
</example>
|
</example>
|
||||||
</refsect1>
|
</refsect1>
|
||||||
|
|
||||||
|
|
|
@ -103,7 +103,7 @@
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>The argument should be a comma-separated list of unit
|
<para>The argument should be a comma-separated list of unit
|
||||||
LOAD, SUB, or ACTIVE states. When listing units, show only
|
LOAD, SUB, or ACTIVE states. When listing units, show only
|
||||||
those in specified states. Use <option>--state=failed</option>
|
those in the specified states. Use <option>--state=failed</option>
|
||||||
to show only failed units.</para>
|
to show only failed units.</para>
|
||||||
|
|
||||||
<para>As a special case, if one of the arguments is
|
<para>As a special case, if one of the arguments is
|
||||||
|
@ -518,7 +518,7 @@
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>When used with
|
<para>When used with
|
||||||
<command>enable</command>/<command>disable</command>/<command>is-enabled</command>
|
<command>enable</command>/<command>disable</command>/<command>is-enabled</command>
|
||||||
(and related commands), use alternative root path when
|
(and related commands), use an alternate root path when
|
||||||
looking for unit files.</para>
|
looking for unit files.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
|
@ -851,7 +851,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
|
||||||
<para>Show properties of one or more units, jobs, or the
|
<para>Show properties of one or more units, jobs, or the
|
||||||
manager itself. If no argument is specified, properties of
|
manager itself. If no argument is specified, properties of
|
||||||
the manager will be shown. If a unit name is specified,
|
the manager will be shown. If a unit name is specified,
|
||||||
properties of the unit is shown, and if a job id is
|
properties of the unit is shown, and if a job ID is
|
||||||
specified, properties of the job is shown. By default, empty
|
specified, properties of the job is shown. By default, empty
|
||||||
properties are suppressed. Use <option>--all</option> to
|
properties are suppressed. Use <option>--all</option> to
|
||||||
show those too. To select specific properties to show, use
|
show those too. To select specific properties to show, use
|
||||||
|
@ -1158,17 +1158,17 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
|
||||||
</row>
|
</row>
|
||||||
<row>
|
<row>
|
||||||
<entry><literal>static</literal></entry>
|
<entry><literal>static</literal></entry>
|
||||||
<entry>Unit file is not enabled, and has no provisions for enabling in the <literal>[Install]</literal> section.</entry>
|
<entry>The unit file is not enabled, and has no provisions for enabling in the <literal>[Install]</literal> section.</entry>
|
||||||
<entry>0</entry>
|
<entry>0</entry>
|
||||||
</row>
|
</row>
|
||||||
<row>
|
<row>
|
||||||
<entry><literal>indirect</literal></entry>
|
<entry><literal>indirect</literal></entry>
|
||||||
<entry>Unit file itself is not enabled, but it has a non-empty <varname>Also=</varname> setting in the <literal>[Install]</literal> section, listing other unit files that might be enabled.</entry>
|
<entry>The unit file itself is not enabled, but it has a non-empty <varname>Also=</varname> setting in the <literal>[Install]</literal> section, listing other unit files that might be enabled.</entry>
|
||||||
<entry>0</entry>
|
<entry>0</entry>
|
||||||
</row>
|
</row>
|
||||||
<row>
|
<row>
|
||||||
<entry><literal>disabled</literal></entry>
|
<entry><literal>disabled</literal></entry>
|
||||||
<entry>Unit file is not enabled.</entry>
|
<entry>The unit file is not enabled.</entry>
|
||||||
<entry>> 0</entry>
|
<entry>> 0</entry>
|
||||||
</row>
|
</row>
|
||||||
</tbody>
|
</tbody>
|
||||||
|
@ -1227,12 +1227,12 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Adds <literal>Wants=</literal> or <literal>Requires=</literal>
|
<para>Adds <literal>Wants=</literal> or <literal>Requires=</literal>
|
||||||
dependency, respectively, to the specified
|
dependencies, respectively, to the specified
|
||||||
<replaceable>TARGET</replaceable> for one or more units. </para>
|
<replaceable>TARGET</replaceable> for one or more units. </para>
|
||||||
|
|
||||||
<para>This command honors <option>--system</option>,
|
<para>This command honors <option>--system</option>,
|
||||||
<option>--user</option>, <option>--runtime</option> and
|
<option>--user</option>, <option>--runtime</option> and
|
||||||
<option>--global</option> in a similar way as
|
<option>--global</option> in a way similar to
|
||||||
<command>enable</command>.</para>
|
<command>enable</command>.</para>
|
||||||
|
|
||||||
</listitem>
|
</listitem>
|
||||||
|
@ -1248,7 +1248,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
|
||||||
|
|
||||||
<para>Depending on whether <option>--system</option> (the default),
|
<para>Depending on whether <option>--system</option> (the default),
|
||||||
<option>--user</option>, or <option>--global</option> is specified,
|
<option>--user</option>, or <option>--global</option> is specified,
|
||||||
this creates a drop-in file for each unit either for the system,
|
this command creates a drop-in file for each unit either for the system,
|
||||||
for the calling user, or for all futures logins of all users. Then,
|
for the calling user, or for all futures logins of all users. Then,
|
||||||
the editor (see the "Environment" section below) is invoked on
|
the editor (see the "Environment" section below) is invoked on
|
||||||
temporary files which will be written to the real location if the
|
temporary files which will be written to the real location if the
|
||||||
|
@ -1442,7 +1442,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
|
||||||
<term><command>daemon-reload</command></term>
|
<term><command>daemon-reload</command></term>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Reload systemd manager configuration. This will
|
<para>Reload the systemd manager configuration. This will
|
||||||
rerun all generators (see
|
rerun all generators (see
|
||||||
<citerefentry><refentrytitle>systemd.generator</refentrytitle><manvolnum>7</manvolnum></citerefentry>),
|
<citerefentry><refentrytitle>systemd.generator</refentrytitle><manvolnum>7</manvolnum></citerefentry>),
|
||||||
reload all unit files, and recreate the entire dependency
|
reload all unit files, and recreate the entire dependency
|
||||||
|
@ -1485,7 +1485,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
|
||||||
maintenance mode, and with no failed services. Failure is
|
maintenance mode, and with no failed services. Failure is
|
||||||
returned otherwise (exit code non-zero). In addition, the
|
returned otherwise (exit code non-zero). In addition, the
|
||||||
current state is printed in a short string to standard
|
current state is printed in a short string to standard
|
||||||
output, see table below. Use <option>--quiet</option> to
|
output, see the table below. Use <option>--quiet</option> to
|
||||||
suppress this output.</para>
|
suppress this output.</para>
|
||||||
|
|
||||||
<table>
|
<table>
|
||||||
|
|
|
@ -139,7 +139,7 @@
|
||||||
any collected passwords into the kernel keyring of the root
|
any collected passwords into the kernel keyring of the root
|
||||||
user, as a key of the specified name. If combined with
|
user, as a key of the specified name. If combined with
|
||||||
<option>--accept-cached</option>, it will also try to retrieve
|
<option>--accept-cached</option>, it will also try to retrieve
|
||||||
the such cached passwords from the key in the kernel keyring
|
such cached passwords from the key in the kernel keyring
|
||||||
instead of querying the user right away. By using this option,
|
instead of querying the user right away. By using this option,
|
||||||
the kernel keyring may be used as effective cache to avoid
|
the kernel keyring may be used as effective cache to avoid
|
||||||
repeatedly asking users for passwords, if there are multiple
|
repeatedly asking users for passwords, if there are multiple
|
||||||
|
@ -181,7 +181,7 @@
|
||||||
<term><option>--accept-cached</option></term>
|
<term><option>--accept-cached</option></term>
|
||||||
|
|
||||||
<listitem><para>If passed, accept cached passwords, i.e.
|
<listitem><para>If passed, accept cached passwords, i.e.
|
||||||
passwords previously typed in. </para></listitem>
|
passwords previously entered.</para></listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
|
|
|
@ -58,8 +58,8 @@
|
||||||
that restores the display backlight brightness at early boot and
|
that restores the display backlight brightness at early boot and
|
||||||
saves it at shutdown. On disk, the backlight brightness is stored
|
saves it at shutdown. On disk, the backlight brightness is stored
|
||||||
in <filename>/var/lib/systemd/backlight/</filename>. During
|
in <filename>/var/lib/systemd/backlight/</filename>. During
|
||||||
loading, if udev property <option>ID_BACKLIGHT_CLAMP</option> is
|
loading, if the udev property <option>ID_BACKLIGHT_CLAMP</option> is
|
||||||
not set to false value, the brightness is clamped to a value of at
|
not set to false, the brightness is clamped to a value of at
|
||||||
least 1 or 5% of maximum brightness, whichever is greater. This
|
least 1 or 5% of maximum brightness, whichever is greater. This
|
||||||
restriction will be removed when the kernel allows user space to
|
restriction will be removed when the kernel allows user space to
|
||||||
reliably set a brightness value which does not turn off the
|
reliably set a brightness value which does not turn off the
|
||||||
|
|
|
@ -203,7 +203,7 @@
|
||||||
<listitem><para>Controls whether the number of processes shown
|
<listitem><para>Controls whether the number of processes shown
|
||||||
for a control group shall include all processes that are
|
for a control group shall include all processes that are
|
||||||
contained in any of the child control groups as well. Takes a
|
contained in any of the child control groups as well. Takes a
|
||||||
boolean argument, defaults to <literal>yes</literal>. If
|
boolean argument, which defaults to <literal>yes</literal>. If
|
||||||
enabled, the processes in child control groups are included, if
|
enabled, the processes in child control groups are included, if
|
||||||
disabled, only the processes in the control group itself are
|
disabled, only the processes in the control group itself are
|
||||||
counted. This setting may also be toggled at runtime by
|
counted. This setting may also be toggled at runtime by
|
||||||
|
@ -343,7 +343,7 @@
|
||||||
excluding processes in child control groups in control group
|
excluding processes in child control groups in control group
|
||||||
process counts. This setting may also be controlled using the
|
process counts. This setting may also be controlled using the
|
||||||
<option>--recursive=</option> command line switch. This key is
|
<option>--recursive=</option> command line switch. This key is
|
||||||
not available of all tasks are counted, it is only available
|
not available if all tasks are counted, it is only available
|
||||||
if processes are counted, as enabled with the
|
if processes are counted, as enabled with the
|
||||||
<keycap>P</keycap> or <keycap>k</keycap>
|
<keycap>P</keycap> or <keycap>k</keycap>
|
||||||
keys.</para></listitem>
|
keys.</para></listitem>
|
||||||
|
|
|
@ -69,9 +69,9 @@
|
||||||
|
|
||||||
<para>By default, this command will escape the strings passed,
|
<para>By default, this command will escape the strings passed,
|
||||||
unless <option>--unescape</option> is passed which results in the
|
unless <option>--unescape</option> is passed which results in the
|
||||||
inverse operation being applied. If <option>--mangle</option> a
|
inverse operation being applied. If <option>--mangle</option> is given, a
|
||||||
special mode of escaping is applied instead, which assumes a
|
special mode of escaping is applied instead, which assumes the
|
||||||
string to be already escaped but will escape everything that
|
string is already escaped but will escape everything that
|
||||||
appears obviously non-escaped.</para>
|
appears obviously non-escaped.</para>
|
||||||
</refsect1>
|
</refsect1>
|
||||||
|
|
||||||
|
|
|
@ -80,8 +80,8 @@
|
||||||
<listitem><para>The root user's password</para></listitem>
|
<listitem><para>The root user's password</para></listitem>
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
|
|
||||||
<para>Each of the fields may either be queried interactively from
|
<para>Each of the fields may either be queried interactively by
|
||||||
the users, set non-interactively on the tool's command line, or be
|
users, set non-interactively on the tool's command line, or be
|
||||||
copied from a host system that is used to set up the system
|
copied from a host system that is used to set up the system
|
||||||
image.</para>
|
image.</para>
|
||||||
|
|
||||||
|
@ -166,9 +166,9 @@
|
||||||
<citerefentry project='die-net'><refentrytitle>shadow</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
<citerefentry project='die-net'><refentrytitle>shadow</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
||||||
file. This setting exists in two forms:
|
file. This setting exists in two forms:
|
||||||
<option>--root-password=</option> accepts the password to set
|
<option>--root-password=</option> accepts the password to set
|
||||||
directly on the command line,
|
directly on the command line, and
|
||||||
<option>--root-password-file=</option> reads it from a file.
|
<option>--root-password-file=</option> reads it from a file.
|
||||||
Note that it is not recommended specifying passwords on the
|
Note that it is not recommended to specify passwords on the
|
||||||
command line, as other users might be able to see them simply
|
command line, as other users might be able to see them simply
|
||||||
by invoking
|
by invoking
|
||||||
<citerefentry project='die-net'><refentrytitle>ps</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para></listitem>
|
<citerefentry project='die-net'><refentrytitle>ps</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para></listitem>
|
||||||
|
|
|
@ -66,11 +66,11 @@
|
||||||
<filename>systemd-fsck@.service</filename> is used for all other
|
<filename>systemd-fsck@.service</filename> is used for all other
|
||||||
file systems and for the root file system in the initramfs.</para>
|
file systems and for the root file system in the initramfs.</para>
|
||||||
|
|
||||||
<para>Those services are started at boot if
|
<para>These services are started at boot if
|
||||||
<option>passno</option> in <filename>/etc/fstab</filename> for the
|
<option>passno</option> in <filename>/etc/fstab</filename> for the
|
||||||
file system is set to a value greater than zero. The file system
|
file system is set to a value greater than zero. The file system
|
||||||
check for root is performed before the other file systems. Other
|
check for root is performed before the other file systems. Other
|
||||||
file systems may be checked in parallel, except when they are one
|
file systems may be checked in parallel, except when they are on
|
||||||
the same rotating disk.</para>
|
the same rotating disk.</para>
|
||||||
|
|
||||||
<para><filename>systemd-fsck</filename> does not know any details
|
<para><filename>systemd-fsck</filename> does not know any details
|
||||||
|
|
|
@ -64,7 +64,7 @@
|
||||||
<term><option>-r</option></term>
|
<term><option>-r</option></term>
|
||||||
<term><option>--root=<replaceable>PATH</replaceable></option></term>
|
<term><option>--root=<replaceable>PATH</replaceable></option></term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Alternative root path in the filesystem.</para>
|
<para>Alternate root path in the filesystem.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
</variablelist>
|
</variablelist>
|
||||||
|
|
|
@ -244,7 +244,7 @@ systemd-tmpfiles --create --prefix /var/log/journal</programlisting>
|
||||||
|
|
||||||
<listitem><para>Sockets and other paths that
|
<listitem><para>Sockets and other paths that
|
||||||
<command>systemd-journald</command> will listen on that are
|
<command>systemd-journald</command> will listen on that are
|
||||||
visible in the file system. In addition to those, journald can
|
visible in the file system. In addition to these, journald can
|
||||||
listen for audit events using netlink.</para></listitem>
|
listen for audit events using netlink.</para></listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
</variablelist>
|
</variablelist>
|
||||||
|
|
|
@ -42,7 +42,7 @@
|
||||||
|
|
||||||
<refnamediv>
|
<refnamediv>
|
||||||
<refname>systemd-machine-id-commit.service</refname>
|
<refname>systemd-machine-id-commit.service</refname>
|
||||||
<refpurpose>Commit a transient machine-id to disk</refpurpose>
|
<refpurpose>Commit a transient machine ID to disk</refpurpose>
|
||||||
</refnamediv>
|
</refnamediv>
|
||||||
|
|
||||||
<refsynopsisdiv>
|
<refsynopsisdiv>
|
||||||
|
|
|
@ -88,7 +88,7 @@
|
||||||
and is different for every booted instance of the
|
and is different for every booted instance of the
|
||||||
VM.</para></listitem>
|
VM.</para></listitem>
|
||||||
|
|
||||||
<listitem><para>Similar, if run inside a Linux container
|
<listitem><para>Similarly, if run inside a Linux container
|
||||||
environment and a UUID is configured for the container, this is
|
environment and a UUID is configured for the container, this is
|
||||||
used to initialize the machine ID. For details, see the
|
used to initialize the machine ID. For details, see the
|
||||||
documentation of the <ulink
|
documentation of the <ulink
|
||||||
|
|
|
@ -125,7 +125,7 @@
|
||||||
message is sent. This option is hence unrelated to the other
|
message is sent. This option is hence unrelated to the other
|
||||||
options. For details about the semantics of this option, see
|
options. For details about the semantics of this option, see
|
||||||
<citerefentry><refentrytitle>sd_booted</refentrytitle><manvolnum>3</manvolnum></citerefentry>. An
|
<citerefentry><refentrytitle>sd_booted</refentrytitle><manvolnum>3</manvolnum></citerefentry>. An
|
||||||
alternative way to check for this state is to call
|
alternate way to check for this state is to call
|
||||||
<citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>
|
<citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>
|
||||||
with the <command>is-system-running</command> command. It will
|
with the <command>is-system-running</command> command. It will
|
||||||
return <literal>offline</literal> if the system was not booted
|
return <literal>offline</literal> if the system was not booted
|
||||||
|
|
|
@ -344,7 +344,7 @@
|
||||||
must be shifted to the container UID base that is
|
must be shifted to the container UID base that is
|
||||||
used during container runtime.</para>
|
used during container runtime.</para>
|
||||||
|
|
||||||
<para>It is recommended to assign as least 65536 UIDs to each
|
<para>It is recommended to assign at least 65536 UIDs to each
|
||||||
container, so that the usable UID range in the container
|
container, so that the usable UID range in the container
|
||||||
covers 16 bit. For best security, do not assign overlapping UID
|
covers 16 bit. For best security, do not assign overlapping UID
|
||||||
ranges to multiple containers. It is hence a good idea to use
|
ranges to multiple containers. It is hence a good idea to use
|
||||||
|
@ -458,7 +458,7 @@
|
||||||
which case <literal>tcp</literal> is assumed. The container
|
which case <literal>tcp</literal> is assumed. The container
|
||||||
port number and its colon may be omitted, in which case the
|
port number and its colon may be omitted, in which case the
|
||||||
same port as the host port is implied. This option is only
|
same port as the host port is implied. This option is only
|
||||||
supported if private networking is used, such as
|
supported if private networking is used, such as with
|
||||||
<option>--network-veth</option> or
|
<option>--network-veth</option> or
|
||||||
<option>--network-bridge=</option>.</para></listitem>
|
<option>--network-bridge=</option>.</para></listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
@ -693,7 +693,7 @@
|
||||||
<listitem><para>Controls whether the container is registered
|
<listitem><para>Controls whether the container is registered
|
||||||
with
|
with
|
||||||
<citerefentry><refentrytitle>systemd-machined</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
|
<citerefentry><refentrytitle>systemd-machined</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
|
||||||
Takes a boolean argument, defaults to <literal>yes</literal>.
|
Takes a boolean argument, which defaults to <literal>yes</literal>.
|
||||||
This option should be enabled when the container runs a full
|
This option should be enabled when the container runs a full
|
||||||
Operating System (more specifically: an init system), and is
|
Operating System (more specifically: an init system), and is
|
||||||
useful to ensure that the container is accessible via
|
useful to ensure that the container is accessible via
|
||||||
|
@ -753,7 +753,7 @@
|
||||||
<listitem><para>Boots the container in volatile mode. When no
|
<listitem><para>Boots the container in volatile mode. When no
|
||||||
mode parameter is passed or when mode is specified as
|
mode parameter is passed or when mode is specified as
|
||||||
<option>yes</option>, full volatile mode is enabled. This
|
<option>yes</option>, full volatile mode is enabled. This
|
||||||
means the root directory is mounted as mostly unpopulated
|
means the root directory is mounted as a mostly unpopulated
|
||||||
<literal>tmpfs</literal> instance, and
|
<literal>tmpfs</literal> instance, and
|
||||||
<filename>/usr</filename> from the OS tree is mounted into it,
|
<filename>/usr</filename> from the OS tree is mounted into it,
|
||||||
read-only (the system thus starts up with read-only OS
|
read-only (the system thus starts up with read-only OS
|
||||||
|
@ -761,9 +761,9 @@
|
||||||
to the either are lost on shutdown). When the mode parameter
|
to the either are lost on shutdown). When the mode parameter
|
||||||
is specified as <option>state</option>, the OS tree is
|
is specified as <option>state</option>, the OS tree is
|
||||||
mounted read-only, but <filename>/var</filename> is mounted as
|
mounted read-only, but <filename>/var</filename> is mounted as
|
||||||
<literal>tmpfs</literal> instance into it (the system thus
|
a <literal>tmpfs</literal> instance into it (the system thus
|
||||||
starts up with read-only OS resources and configuration, but
|
starts up with read-only OS resources and configuration, but
|
||||||
pristine state, any changes to the latter are lost on
|
pristine state, and any changes to the latter are lost on
|
||||||
shutdown). When the mode parameter is specified as
|
shutdown). When the mode parameter is specified as
|
||||||
<option>no</option> (the default), the whole OS tree is made
|
<option>no</option> (the default), the whole OS tree is made
|
||||||
available writable.</para>
|
available writable.</para>
|
||||||
|
@ -816,7 +816,7 @@
|
||||||
|
|
||||||
<para>If this option is set to <option>trusted</option>, the
|
<para>If this option is set to <option>trusted</option>, the
|
||||||
file is searched, read and used the same way, but regardless
|
file is searched, read and used the same way, but regardless
|
||||||
if found in <filename>/etc/systemd/nspawn/</filename>,
|
of being found in <filename>/etc/systemd/nspawn/</filename>,
|
||||||
<filename>/run/systemd/nspawn/</filename> or next to the image
|
<filename>/run/systemd/nspawn/</filename> or next to the image
|
||||||
file or container root directory, all settings will take
|
file or container root directory, all settings will take
|
||||||
effect, however, command line arguments still take precedence
|
effect, however, command line arguments still take precedence
|
||||||
|
|
|
@ -75,7 +75,7 @@
|
||||||
<citerefentry><refentrytitle>systemd.network</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
<citerefentry><refentrytitle>systemd.network</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
||||||
for details. To improve compatibility,
|
for details. To improve compatibility,
|
||||||
<filename>/etc/resolv.conf</filename> is read in order to discover
|
<filename>/etc/resolv.conf</filename> is read in order to discover
|
||||||
configured system DNS servers, however only if it is not a symlink
|
configured system DNS servers, but only if it is not a symlink
|
||||||
to <filename>/run/systemd/resolve/resolv.conf</filename> (see above).</para>
|
to <filename>/run/systemd/resolve/resolv.conf</filename> (see above).</para>
|
||||||
|
|
||||||
<para><command>systemd-resolved</command> synthesizes DNS RRs for the following cases:</para>
|
<para><command>systemd-resolved</command> synthesizes DNS RRs for the following cases:</para>
|
||||||
|
|
|
@ -239,7 +239,7 @@
|
||||||
<term><option>--pty</option></term>
|
<term><option>--pty</option></term>
|
||||||
<term><option>-t</option></term>
|
<term><option>-t</option></term>
|
||||||
|
|
||||||
<listitem><para>When invoking a command as service connects
|
<listitem><para>When invoking a command, the service connects
|
||||||
its standard input and output to the invoking tty via a
|
its standard input and output to the invoking tty via a
|
||||||
pseudo TTY device. This allows invoking binaries as services
|
pseudo TTY device. This allows invoking binaries as services
|
||||||
that expect interactive user input, such as interactive
|
that expect interactive user input, such as interactive
|
||||||
|
|
|
@ -74,7 +74,7 @@
|
||||||
specified in
|
specified in
|
||||||
<citerefentry><refentrytitle>sysusers.d</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
<citerefentry><refentrytitle>sysusers.d</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
||||||
are searched for a matching file. If the string
|
are searched for a matching file. If the string
|
||||||
<filename>-</filename> is specified as filenames, entries from the
|
<filename>-</filename> is specified as filename, entries from the
|
||||||
standard input of the process are read.</para>
|
standard input of the process are read.</para>
|
||||||
</refsect1>
|
</refsect1>
|
||||||
|
|
||||||
|
|
|
@ -63,7 +63,7 @@
|
||||||
<para><ulink url="http://refspecs.linuxbase.org/LSB_3.1.1/LSB-Core-generic/LSB-Core-generic/iniscrptact.html">LSB headers</ulink>
|
<para><ulink url="http://refspecs.linuxbase.org/LSB_3.1.1/LSB-Core-generic/LSB-Core-generic/iniscrptact.html">LSB headers</ulink>
|
||||||
in SysV init scripts are interpreted, and the ordering specified
|
in SysV init scripts are interpreted, and the ordering specified
|
||||||
in the header is turned into dependencies between the generated
|
in the header is turned into dependencies between the generated
|
||||||
unit and other units. LSB facilities
|
unit and other units. The LSB facilities
|
||||||
<literal>$remote_fs</literal>, <literal>$network</literal>,
|
<literal>$remote_fs</literal>, <literal>$network</literal>,
|
||||||
<literal>$named</literal>, <literal>$portmap</literal>,
|
<literal>$named</literal>, <literal>$portmap</literal>,
|
||||||
<literal>$time</literal> are supported and will be turned into
|
<literal>$time</literal> are supported and will be turned into
|
||||||
|
@ -73,7 +73,7 @@
|
||||||
|
|
||||||
<para>SysV runlevels have corresponding systemd targets
|
<para>SysV runlevels have corresponding systemd targets
|
||||||
(<filename>runlevel<replaceable>X</replaceable>.target</filename>).
|
(<filename>runlevel<replaceable>X</replaceable>.target</filename>).
|
||||||
Wrapper unit that is generated will be wanted by those targets
|
The wrapper unit that is generated will be wanted by those targets
|
||||||
which correspond to runlevels for which the script is
|
which correspond to runlevels for which the script is
|
||||||
enabled.</para>
|
enabled.</para>
|
||||||
|
|
||||||
|
|
|
@ -85,7 +85,7 @@
|
||||||
<term><filename>/var/lib/systemd/clock</filename></term>
|
<term><filename>/var/lib/systemd/clock</filename></term>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>This file contains the timestamp of last successful
|
<para>This file contains the timestamp of the last successful
|
||||||
synchronization.</para>
|
synchronization.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
|
@ -58,7 +58,7 @@
|
||||||
service that is invoked as part of the first boot after the vendor
|
service that is invoked as part of the first boot after the vendor
|
||||||
operating system resources in <filename>/usr</filename> have been
|
operating system resources in <filename>/usr</filename> have been
|
||||||
updated. This is useful to implement offline updates of
|
updated. This is useful to implement offline updates of
|
||||||
<filename>/usr</filename> which might requires updates to
|
<filename>/usr</filename> which might require updates to
|
||||||
<filename>/etc</filename> or <filename>/var</filename> on the
|
<filename>/etc</filename> or <filename>/var</filename> on the
|
||||||
following boot.</para>
|
following boot.</para>
|
||||||
|
|
||||||
|
|
|
@ -137,7 +137,7 @@
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><varname>TimeoutIdleSec=</varname></term>
|
<term><varname>TimeoutIdleSec=</varname></term>
|
||||||
<listitem><para>Configures an idleness timeout. Once the mount has been
|
<listitem><para>Configures an idle timeout. Once the mount has been
|
||||||
idle for the specified time, systemd will attempt to unmount. Takes a
|
idle for the specified time, systemd will attempt to unmount. Takes a
|
||||||
unit-less value in seconds, or a time span value such as "5min 20s".
|
unit-less value in seconds, or a time span value such as "5min 20s".
|
||||||
Pass 0 to disable the timeout logic. The timeout is disabled by
|
Pass 0 to disable the timeout logic. The timeout is disabled by
|
||||||
|
|
|
@ -493,7 +493,7 @@
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><varname>SyslogLevel=</varname></term>
|
<term><varname>SyslogLevel=</varname></term>
|
||||||
<listitem><para>Default syslog level to use when logging to
|
<listitem><para>The default syslog level to use when logging to
|
||||||
syslog or the kernel log buffer. One of
|
syslog or the kernel log buffer. One of
|
||||||
<option>emerg</option>,
|
<option>emerg</option>,
|
||||||
<option>alert</option>,
|
<option>alert</option>,
|
||||||
|
@ -951,13 +951,13 @@
|
||||||
invoked process must implement a
|
invoked process must implement a
|
||||||
<command>getty</command>-compatible utmp/wtmp logic. If
|
<command>getty</command>-compatible utmp/wtmp logic. If
|
||||||
<literal>login</literal> is set, first an
|
<literal>login</literal> is set, first an
|
||||||
<constant>INIT_PROCESS</constant> entry, followed by an
|
<constant>INIT_PROCESS</constant> entry, followed by a
|
||||||
<constant>LOGIN_PROCESS</constant> entry is generated. In
|
<constant>LOGIN_PROCESS</constant> entry is generated. In
|
||||||
this case, the invoked process must implement a <citerefentry
|
this case, the invoked process must implement a <citerefentry
|
||||||
project='die-net'><refentrytitle>login</refentrytitle><manvolnum>1</manvolnum></citerefentry>-compatible
|
project='die-net'><refentrytitle>login</refentrytitle><manvolnum>1</manvolnum></citerefentry>-compatible
|
||||||
utmp/wtmp logic. If <literal>user</literal> is set, first an
|
utmp/wtmp logic. If <literal>user</literal> is set, first an
|
||||||
<constant>INIT_PROCESS</constant> entry, then a
|
<constant>INIT_PROCESS</constant> entry, then a
|
||||||
<constant>LOGIN_PROCESS</constant> entry and finally an
|
<constant>LOGIN_PROCESS</constant> entry and finally a
|
||||||
<constant>USER_PROCESS</constant> entry is generated. In this
|
<constant>USER_PROCESS</constant> entry is generated. In this
|
||||||
case, the invoked process may be any process that is suitable
|
case, the invoked process may be any process that is suitable
|
||||||
to be run as session leader. Defaults to
|
to be run as session leader. Defaults to
|
||||||
|
|
|
@ -87,7 +87,7 @@
|
||||||
dynamically into native unit files.</para>
|
dynamically into native unit files.</para>
|
||||||
|
|
||||||
<para>Generators are loaded from a set of paths determined during
|
<para>Generators are loaded from a set of paths determined during
|
||||||
compilation, listed above. System and user generators are loaded
|
compilation, as listed above. System and user generators are loaded
|
||||||
from directories with names ending in
|
from directories with names ending in
|
||||||
<filename>system-generators/</filename> and
|
<filename>system-generators/</filename> and
|
||||||
<filename>user-generators/</filename>, respectively. Generators
|
<filename>user-generators/</filename>, respectively. Generators
|
||||||
|
@ -169,14 +169,14 @@
|
||||||
or <command>systemd</command> itself (this means: no
|
or <command>systemd</command> itself (this means: no
|
||||||
<citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>!). They
|
<citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>!). They
|
||||||
can however rely on the most basic kernel functionality to
|
can however rely on the most basic kernel functionality to
|
||||||
be available, including mounted <filename>/sys</filename>,
|
be available, including a mounted <filename>/sys</filename>,
|
||||||
<filename>/proc</filename>, <filename>/dev</filename>.
|
<filename>/proc</filename>, <filename>/dev</filename>.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Units written by generators are removed when configuration
|
Units written by generators are removed when the configuration
|
||||||
is reloaded. That means the lifetime of the generated
|
is reloaded. That means the lifetime of the generated
|
||||||
units is closely bound to the reload cycles of
|
units is closely bound to the reload cycles of
|
||||||
<command>systemd</command> itself.
|
<command>systemd</command> itself.
|
||||||
|
@ -233,7 +233,7 @@
|
||||||
<para>
|
<para>
|
||||||
If you are careful, you can implement generators in shell
|
If you are careful, you can implement generators in shell
|
||||||
scripts. We do recommend C code however, since generators
|
scripts. We do recommend C code however, since generators
|
||||||
delay are executed synchronously and hence delay the
|
are executed synchronously and hence delay the
|
||||||
entire boot if they are slow.
|
entire boot if they are slow.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
|
@ -70,7 +70,7 @@
|
||||||
name in <filename>/usr/lib</filename>. This can be used to
|
name in <filename>/usr/lib</filename>. This can be used to
|
||||||
override a system-supplied link file with a local file if needed.
|
override a system-supplied link file with a local file if needed.
|
||||||
As a special case, an empty file (file size 0) or symlink with the
|
As a special case, an empty file (file size 0) or symlink with the
|
||||||
same name pointing to <filename>/dev/null</filename> disable the
|
same name pointing to <filename>/dev/null</filename> disables the
|
||||||
configuration file entirely (it is "masked").</para>
|
configuration file entirely (it is "masked").</para>
|
||||||
|
|
||||||
<para>The link file contains a <literal>[Match]</literal> section,
|
<para>The link file contains a <literal>[Match]</literal> section,
|
||||||
|
@ -217,7 +217,7 @@
|
||||||
generated which is guaranteed to be the same on every
|
generated which is guaranteed to be the same on every
|
||||||
boot for the given machine and the given device, but
|
boot for the given machine and the given device, but
|
||||||
which is otherwise random. This feature depends on ID_NET_NAME_*
|
which is otherwise random. This feature depends on ID_NET_NAME_*
|
||||||
properties existing for the link. On hardware where these
|
properties to exist for the link. On hardware where these
|
||||||
properties are not set, the generation of a persistent MAC address
|
properties are not set, the generation of a persistent MAC address
|
||||||
will fail.</para>
|
will fail.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
|
@ -180,7 +180,7 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><option>x-systemd.idle-timeout=</option></term>
|
<term><option>x-systemd.idle-timeout=</option></term>
|
||||||
|
|
||||||
<listitem><para>Configures the idleness timeout of the
|
<listitem><para>Configures the idle timeout of the
|
||||||
automount unit. See <varname>TimeoutIdleSec=</varname> in
|
automount unit. See <varname>TimeoutIdleSec=</varname> in
|
||||||
<citerefentry><refentrytitle>systemd.automount</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
<citerefentry><refentrytitle>systemd.automount</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
||||||
for details.</para></listitem>
|
for details.</para></listitem>
|
||||||
|
@ -192,13 +192,13 @@
|
||||||
<listitem><para>Configure how long systemd should wait for a
|
<listitem><para>Configure how long systemd should wait for a
|
||||||
device to show up before giving up on an entry from
|
device to show up before giving up on an entry from
|
||||||
<filename>/etc/fstab</filename>. Specify a time in seconds or
|
<filename>/etc/fstab</filename>. Specify a time in seconds or
|
||||||
explicitly append a unit as <literal>s</literal>,
|
explicitly append a unit such as <literal>s</literal>,
|
||||||
<literal>min</literal>, <literal>h</literal>,
|
<literal>min</literal>, <literal>h</literal>,
|
||||||
<literal>ms</literal>.</para>
|
<literal>ms</literal>.</para>
|
||||||
|
|
||||||
<para>Note that this option can only be used in
|
<para>Note that this option can only be used in
|
||||||
<filename>/etc/fstab</filename>, and will be
|
<filename>/etc/fstab</filename>, and will be
|
||||||
ignored when part of <varname>Options=</varname>
|
ignored when part of the <varname>Options=</varname>
|
||||||
setting in a unit file.</para>
|
setting in a unit file.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
@ -212,7 +212,7 @@
|
||||||
<filename>local-fs.target</filename> or
|
<filename>local-fs.target</filename> or
|
||||||
<filename>remote-fs.target</filename>. This means that it will
|
<filename>remote-fs.target</filename>. This means that it will
|
||||||
not be mounted automatically during boot, unless it is pulled
|
not be mounted automatically during boot, unless it is pulled
|
||||||
in by some other unit. Option <option>auto</option> has the
|
in by some other unit. The <option>auto</option> option has the
|
||||||
opposite meaning and is the default.</para>
|
opposite meaning and is the default.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
@ -325,11 +325,11 @@
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><varname>SmackFileSystemRootLabel=</varname></term>
|
<term><varname>SmackFileSystemRootLabel=</varname></term>
|
||||||
<listitem><para>Takes a string for the smack label.
|
<listitem><para>Takes a string for the SMACK label.
|
||||||
This option specifies the label to assign the root of the
|
This option specifies the label to assign the root of the
|
||||||
file system if it lacks the Smack extended attribute.
|
file system if it lacks the SMACK extended attribute.
|
||||||
Note that this option will be ignored if kernel does not
|
Note that this option will be ignored if kernel does not
|
||||||
support the Smack feature.
|
support the SMACK feature.
|
||||||
See <ulink
|
See <ulink
|
||||||
url="https://www.kernel.org/doc/Documentation/security/Smack.txt">Smack.txt</ulink>
|
url="https://www.kernel.org/doc/Documentation/security/Smack.txt">Smack.txt</ulink>
|
||||||
for details. </para></listitem>
|
for details. </para></listitem>
|
||||||
|
|
|
@ -82,7 +82,7 @@
|
||||||
override a system-supplied configuration file with a local file if
|
override a system-supplied configuration file with a local file if
|
||||||
needed. As a special case, an empty file (file size 0) or symlink
|
needed. As a special case, an empty file (file size 0) or symlink
|
||||||
with the same name pointing to <filename>/dev/null</filename>
|
with the same name pointing to <filename>/dev/null</filename>
|
||||||
disable the configuration file entirely (it is "masked").</para>
|
disables the configuration file entirely (it is "masked").</para>
|
||||||
</refsect1>
|
</refsect1>
|
||||||
|
|
||||||
<refsect1>
|
<refsect1>
|
||||||
|
@ -106,7 +106,7 @@
|
||||||
<entry>A bond device is an aggregation of all its slave devices. See <ulink url="https://www.kernel.org/doc/Documentation/networking/bonding.txt">Linux Ethernet Bonding Driver HOWTO</ulink> for details.Local configuration</entry></row>
|
<entry>A bond device is an aggregation of all its slave devices. See <ulink url="https://www.kernel.org/doc/Documentation/networking/bonding.txt">Linux Ethernet Bonding Driver HOWTO</ulink> for details.Local configuration</entry></row>
|
||||||
|
|
||||||
<row><entry><varname>bridge</varname></entry>
|
<row><entry><varname>bridge</varname></entry>
|
||||||
<entry>A bridge device is a software switch, each of its slave devices and the bridge itself are ports of the switch.</entry></row>
|
<entry>A bridge device is a software switch, and each of its slave devices and the bridge itself are ports of the switch.</entry></row>
|
||||||
|
|
||||||
<row><entry><varname>dummy</varname></entry>
|
<row><entry><varname>dummy</varname></entry>
|
||||||
<entry>A dummy device drops all packets sent to it.</entry></row>
|
<entry>A dummy device drops all packets sent to it.</entry></row>
|
||||||
|
@ -148,7 +148,7 @@
|
||||||
<entry>A persistent Level 3 tunnel between a network device and a device node.</entry></row>
|
<entry>A persistent Level 3 tunnel between a network device and a device node.</entry></row>
|
||||||
|
|
||||||
<row><entry><varname>veth</varname></entry>
|
<row><entry><varname>veth</varname></entry>
|
||||||
<entry>An ethernet tunnel between a pair of network devices.</entry></row>
|
<entry>An Ethernet tunnel between a pair of network devices.</entry></row>
|
||||||
|
|
||||||
<row><entry><varname>vlan</varname></entry>
|
<row><entry><varname>vlan</varname></entry>
|
||||||
<entry>A VLAN is a stacked device which receives packets from its underlying device based on VLAN tagging. See <ulink url="http://www.ieee802.org/1/pages/802.1Q.html">IEEE 802.1Q</ulink> for details.</entry></row>
|
<entry>A VLAN is a stacked device which receives packets from its underlying device based on VLAN tagging. See <ulink url="http://www.ieee802.org/1/pages/802.1Q.html">IEEE 802.1Q</ulink> for details.</entry></row>
|
||||||
|
@ -282,13 +282,13 @@
|
||||||
|
|
||||||
<para>The <literal>[Bridge]</literal> section only applies for
|
<para>The <literal>[Bridge]</literal> section only applies for
|
||||||
netdevs of kind <literal>bridge</literal>, and accepts the
|
netdevs of kind <literal>bridge</literal>, and accepts the
|
||||||
following key:</para>
|
following keys:</para>
|
||||||
|
|
||||||
<variablelist class='network-directives'>
|
<variablelist class='network-directives'>
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><varname>HelloTimeSec=</varname></term>
|
<term><varname>HelloTimeSec=</varname></term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>HelloTimeSec specifies the number of seconds a hello packet is
|
<para>HelloTimeSec specifies the number of seconds between two hello packets
|
||||||
sent out by the root bridge and the designated bridges. Hello packets are
|
sent out by the root bridge and the designated bridges. Hello packets are
|
||||||
used to communicate information about the topology throughout the entire
|
used to communicate information about the topology throughout the entire
|
||||||
bridged local area network.</para>
|
bridged local area network.</para>
|
||||||
|
@ -436,7 +436,7 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><varname>ARPProxy=</varname></term>
|
<term><varname>ARPProxy=</varname></term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>A boolean. When true, enables ARP proxy.</para>
|
<para>A boolean. When true, enables ARP proxying.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
|
@ -449,14 +449,14 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><varname>L3MissNotification=</varname></term>
|
<term><varname>L3MissNotification=</varname></term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>A boolean. When true, enables netlink IP ADDR miss
|
<para>A boolean. When true, enables netlink IP address miss
|
||||||
notifications.</para>
|
notifications.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><varname>RouteShortCircuit=</varname></term>
|
<term><varname>RouteShortCircuit=</varname></term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>A boolean. When true, route short circuit is turned
|
<para>A boolean. When true, route short circuiting is turned
|
||||||
on.</para>
|
on.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
@ -549,14 +549,14 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><varname>IPv6FlowLabel=</varname></term>
|
<term><varname>IPv6FlowLabel=</varname></term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Configures The 20-bit Flow Label (see <ulink url="https://tools.ietf.org/html/rfc6437">
|
<para>Configures the 20-bit flow label (see <ulink url="https://tools.ietf.org/html/rfc6437">
|
||||||
RFC 6437</ulink>) field in the IPv6 header (see <ulink url="https://tools.ietf.org/html/rfc2460">
|
RFC 6437</ulink>) field in the IPv6 header (see <ulink url="https://tools.ietf.org/html/rfc2460">
|
||||||
RFC 2460</ulink>), is used by a node to label packets of a flow.
|
RFC 2460</ulink>), which is used by a node to label packets of a flow.
|
||||||
It's only used for IPv6 Tunnels.
|
It is only used for IPv6 tunnels.
|
||||||
A Flow Label of zero is used to indicate packets that have
|
A flow label of zero is used to indicate packets that have
|
||||||
not been labeled. Takes following values.
|
not been labeled.
|
||||||
When <literal>inherit</literal> it uses the original flowlabel,
|
It can be configured to a value in the range 0–0xFFFFF, or be
|
||||||
or can be configured to any value between 0 to 0xFFFFF.</para>
|
set to <literal>inherit</literal>, in which case the original flowlabel is used.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
|
@ -587,7 +587,7 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><varname>Mode=</varname></term>
|
<term><varname>Mode=</varname></term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>An <literal>ip6tnl</literal> tunnels can have three
|
<para>An <literal>ip6tnl</literal> tunnel can be in one of three
|
||||||
modes
|
modes
|
||||||
<literal>ip6ip6</literal> for IPv6 over IPv6,
|
<literal>ip6ip6</literal> for IPv6 over IPv6,
|
||||||
<literal>ipip6</literal> for IPv4 over IPv6 or
|
<literal>ipip6</literal> for IPv4 over IPv6 or
|
||||||
|
@ -602,7 +602,7 @@
|
||||||
|
|
||||||
<para>The <literal>[Peer]</literal> section only applies for
|
<para>The <literal>[Peer]</literal> section only applies for
|
||||||
netdevs of kind <literal>veth</literal> and accepts the
|
netdevs of kind <literal>veth</literal> and accepts the
|
||||||
following key:</para>
|
following keys:</para>
|
||||||
|
|
||||||
<variablelist class='network-directives'>
|
<variablelist class='network-directives'>
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
|
@ -777,9 +777,9 @@
|
||||||
<term><varname>LearnPacketIntervalSec=</varname></term>
|
<term><varname>LearnPacketIntervalSec=</varname></term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Specifies the number of seconds between instances where the bonding
|
<para>Specifies the number of seconds between instances where the bonding
|
||||||
driver sends learning packets to each slaves peer switch.
|
driver sends learning packets to each slave peer switch.
|
||||||
The valid range is 1–0x7fffffff; the default value is 1. This Option
|
The valid range is 1–0x7fffffff; the default value is 1. This option
|
||||||
has effect only in balance-tlb and balance-alb modes.</para>
|
has an effect only for the balance-tlb and balance-alb modes.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
|
@ -788,8 +788,8 @@
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Specifies the 802.3ad aggregation selection logic to use. Possible values are
|
<para>Specifies the 802.3ad aggregation selection logic to use. Possible values are
|
||||||
<literal>stable</literal>,
|
<literal>stable</literal>,
|
||||||
<literal>bandwidth</literal>,
|
<literal>bandwidth</literal> and
|
||||||
<literal>count</literal>
|
<literal>count</literal>.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
@ -797,13 +797,13 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><varname>FailOverMACPolicy=</varname></term>
|
<term><varname>FailOverMACPolicy=</varname></term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Specifies whether active-backup mode should set all slaves to
|
<para>Specifies whether the active-backup mode should set all slaves to
|
||||||
the same MAC address at enslavement or, when enabled, perform special handling of the
|
the same MAC address at the time of enslavement or, when enabled, to perform special handling of the
|
||||||
bond's MAC address in accordance with the selected policy. The default policy is none.
|
bond's MAC address in accordance with the selected policy. The default policy is none.
|
||||||
Possible values are
|
Possible values are
|
||||||
<literal>none</literal>,
|
<literal>none</literal>,
|
||||||
<literal>active</literal>,
|
<literal>active</literal> and
|
||||||
<literal>follow</literal>
|
<literal>follow</literal>.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
@ -817,8 +817,8 @@
|
||||||
monitoring purposes. Possible values are
|
monitoring purposes. Possible values are
|
||||||
<literal>none</literal>,
|
<literal>none</literal>,
|
||||||
<literal>active</literal>,
|
<literal>active</literal>,
|
||||||
<literal>backup</literal>,
|
<literal>backup</literal> and
|
||||||
<literal>all</literal>
|
<literal>all</literal>.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
@ -838,7 +838,7 @@
|
||||||
<para>Specifies the IP addresses to use as ARP monitoring peers when
|
<para>Specifies the IP addresses to use as ARP monitoring peers when
|
||||||
ARPIntervalSec is greater than 0. These are the targets of the ARP request
|
ARPIntervalSec is greater than 0. These are the targets of the ARP request
|
||||||
sent to determine the health of the link to the targets.
|
sent to determine the health of the link to the targets.
|
||||||
Specify these values in ipv4 dotted decimal format. At least one IP
|
Specify these values in IPv4 dotted decimal format. At least one IP
|
||||||
address must be given for ARP monitoring to function. The
|
address must be given for ARP monitoring to function. The
|
||||||
maximum number of targets that can be specified is 16. The
|
maximum number of targets that can be specified is 16. The
|
||||||
default value is no IP addresses.
|
default value is no IP addresses.
|
||||||
|
@ -853,8 +853,8 @@
|
||||||
in order for the ARP monitor to consider a slave as being up.
|
in order for the ARP monitor to consider a slave as being up.
|
||||||
This option affects only active-backup mode for slaves with
|
This option affects only active-backup mode for slaves with
|
||||||
ARPValidate enabled. Possible values are
|
ARPValidate enabled. Possible values are
|
||||||
<literal>any</literal>,
|
<literal>any</literal> and
|
||||||
<literal>all</literal>
|
<literal>all</literal>.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
@ -868,8 +868,8 @@
|
||||||
occurs. This option is designed to prevent flip-flopping between
|
occurs. This option is designed to prevent flip-flopping between
|
||||||
the primary slave and other slaves. Possible values are
|
the primary slave and other slaves. Possible values are
|
||||||
<literal>always</literal>,
|
<literal>always</literal>,
|
||||||
<literal>better</literal>,
|
<literal>better</literal> and
|
||||||
<literal>failure</literal>
|
<literal>failure</literal>.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
@ -893,7 +893,7 @@
|
||||||
<para>Specify the number of packets to transmit through a slave before
|
<para>Specify the number of packets to transmit through a slave before
|
||||||
moving to the next one. When set to 0, then a slave is chosen at
|
moving to the next one. When set to 0, then a slave is chosen at
|
||||||
random. The valid range is 0–65535. Defaults to 1. This option
|
random. The valid range is 0–65535. Defaults to 1. This option
|
||||||
has effect only in balance-rr mode.
|
only has effect when in balance-rr mode.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
@ -907,7 +907,7 @@
|
||||||
a peer notification is sent on the bonding device and each
|
a peer notification is sent on the bonding device and each
|
||||||
VLAN sub-device. This is repeated at each link monitor interval
|
VLAN sub-device. This is repeated at each link monitor interval
|
||||||
(ARPIntervalSec or MIIMonitorSec, whichever is active) if the number is
|
(ARPIntervalSec or MIIMonitorSec, whichever is active) if the number is
|
||||||
greater than 1. The valid range is 0–255. Default value is 1.
|
greater than 1. The valid range is 0–255. The default value is 1.
|
||||||
These options affect only the active-backup mode.
|
These options affect only the active-backup mode.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
@ -916,8 +916,8 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><varname>AllSlavesActive=</varname></term>
|
<term><varname>AllSlavesActive=</varname></term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para> A boolean. Specifies that duplicate frames (received on inactive ports)
|
<para>A boolean. Specifies that duplicate frames (received on inactive ports)
|
||||||
should be dropped false or delivered true. Normally, bonding will drop
|
should be dropped when false, or delivered when true. Normally, bonding will drop
|
||||||
duplicate frames (received on inactive ports), which is desirable for
|
duplicate frames (received on inactive ports), which is desirable for
|
||||||
most users. But there are some times it is nice to allow duplicate
|
most users. But there are some times it is nice to allow duplicate
|
||||||
frames to be delivered. The default value is false (drop duplicate frames
|
frames to be delivered. The default value is false (drop duplicate frames
|
||||||
|
|
|
@ -78,7 +78,7 @@
|
||||||
override a system-supplied configuration file with a local file if
|
override a system-supplied configuration file with a local file if
|
||||||
needed. As a special case, an empty file (file size 0) or symlink
|
needed. As a special case, an empty file (file size 0) or symlink
|
||||||
with the same name pointing to <filename>/dev/null</filename>
|
with the same name pointing to <filename>/dev/null</filename>
|
||||||
disable the configuration file entirely (it is "masked").</para>
|
disables the configuration file entirely (it is "masked").</para>
|
||||||
</refsect1>
|
</refsect1>
|
||||||
|
|
||||||
<refsect1>
|
<refsect1>
|
||||||
|
@ -263,7 +263,7 @@
|
||||||
<term><varname>IPv6Token=</varname></term>
|
<term><varname>IPv6Token=</varname></term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>An IPv6 address with the top 64 bits unset. When set, indicates the
|
<para>An IPv6 address with the top 64 bits unset. When set, indicates the
|
||||||
64 bits interface part of SLAAC IPv6 addresses for this link. By default,
|
64-bit interface part of SLAAC IPv6 addresses for this link. By default,
|
||||||
it is autogenerated.</para>
|
it is autogenerated.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
@ -409,7 +409,7 @@
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><varname>IPv6AcceptRouterAdvertisements=</varname></term>
|
<term><varname>IPv6AcceptRouterAdvertisements=</varname></term>
|
||||||
<listitem><para>Force the setting of <filename>accept_ra</filename>
|
<listitem><para>Force the setting of the <filename>accept_ra</filename>
|
||||||
(router advertisements) setting for the interface.
|
(router advertisements) setting for the interface.
|
||||||
When unset, the kernel default is used, and router
|
When unset, the kernel default is used, and router
|
||||||
advertisements are accepted only when local forwarding
|
advertisements are accepted only when local forwarding
|
||||||
|
@ -427,8 +427,8 @@
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><varname>IPv6DuplicateAddressDetection=</varname></term>
|
<term><varname>IPv6DuplicateAddressDetection=</varname></term>
|
||||||
<listitem><para>Configures amount of IPv6 Duplicate
|
<listitem><para>Configures the amount of IPv6 Duplicate
|
||||||
Address Detection probes to se(DAD). Defaults to unset.
|
Address Detection (DAD) probes to send. Defaults to unset.
|
||||||
</para></listitem>
|
</para></listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
|
@ -556,7 +556,7 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><varname>Scope=</varname></term>
|
<term><varname>Scope=</varname></term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>The scope of the route. One of the values <literal>global</literal>,
|
<para>The scope of the route, which can be <literal>global</literal>,
|
||||||
<literal>link</literal> or <literal>host</literal>. Defaults to
|
<literal>link</literal> or <literal>host</literal>. Defaults to
|
||||||
<literal>global</literal>.</para>
|
<literal>global</literal>.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
@ -648,7 +648,7 @@
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>When true (the default), the static routes will be
|
<para>When true (the default), the static routes will be
|
||||||
requested from the DHCP server and added to the routing
|
requested from the DHCP server and added to the routing
|
||||||
table with metric of 1024.</para>
|
table with a metric of 1024.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
|
@ -770,7 +770,7 @@
|
||||||
into account that acquire DNS or NTP server information at a
|
into account that acquire DNS or NTP server information at a
|
||||||
later point. DNS server propagation does not take
|
later point. DNS server propagation does not take
|
||||||
<filename>/etc/resolv.conf</filename> into account. Also, note
|
<filename>/etc/resolv.conf</filename> into account. Also, note
|
||||||
that the leases are not refreshed if uplink network
|
that the leases are not refreshed if the uplink network
|
||||||
configuration changes. To ensure clients regularly acquire the
|
configuration changes. To ensure clients regularly acquire the
|
||||||
most current uplink DNS server information, it is thus
|
most current uplink DNS server information, it is thus
|
||||||
advisable to shorten the DHCP lease time via
|
advisable to shorten the DHCP lease time via
|
||||||
|
@ -844,7 +844,7 @@
|
||||||
<term><varname>FastLeave=</varname></term>
|
<term><varname>FastLeave=</varname></term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>A boolean. This flag allows the bridge to immediately stop multicast
|
<para>A boolean. This flag allows the bridge to immediately stop multicast
|
||||||
traffic on a port that receives IGMP Leave message. It is only used with
|
traffic on a port that receives an IGMP Leave message. It is only used with
|
||||||
IGMP snooping if enabled on the bridge. Defaults to off.</para>
|
IGMP snooping if enabled on the bridge. Defaults to off.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
@ -860,7 +860,7 @@
|
||||||
<term><varname>Cost=</varname></term>
|
<term><varname>Cost=</varname></term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Sets the "cost" of sending packets of this interface.
|
<para>Sets the "cost" of sending packets of this interface.
|
||||||
Each port in a bridge may have different speed and the cost
|
Each port in a bridge may have a different speed and the cost
|
||||||
is used to decide which link to use. Faster interfaces
|
is used to decide which link to use. Faster interfaces
|
||||||
should have lower costs.</para>
|
should have lower costs.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
@ -885,8 +885,8 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><varname>VLANId=</varname></term>
|
<term><varname>VLANId=</varname></term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>The VLAN Id for the new static MAC table entry. If
|
<para>The VLAN ID for the new static MAC table entry. If
|
||||||
omitted, no VLAN Id info is appended to the new static MAC
|
omitted, no VLAN ID info is appended to the new static MAC
|
||||||
table entry.</para>
|
table entry.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
|
@ -73,7 +73,7 @@
|
||||||
to specific containers. The syntax of these files is inspired by
|
to specific containers. The syntax of these files is inspired by
|
||||||
<filename>.desktop</filename> files following the <ulink
|
<filename>.desktop</filename> files following the <ulink
|
||||||
url="http://standards.freedesktop.org/desktop-entry-spec/latest/">XDG
|
url="http://standards.freedesktop.org/desktop-entry-spec/latest/">XDG
|
||||||
Desktop Entry Specification</ulink>, which are in turn inspired by
|
Desktop Entry Specification</ulink>, which in turn are inspired by
|
||||||
Microsoft Windows <filename>.ini</filename> files.</para>
|
Microsoft Windows <filename>.ini</filename> files.</para>
|
||||||
|
|
||||||
<para>Boolean arguments used in these settings files can be
|
<para>Boolean arguments used in these settings files can be
|
||||||
|
@ -112,7 +112,7 @@
|
||||||
host (such as files or directories) are ignored. To which options
|
host (such as files or directories) are ignored. To which options
|
||||||
this applies is documented below.</para>
|
this applies is documented below.</para>
|
||||||
|
|
||||||
<para>Persistent settings file created and maintained by the
|
<para>Persistent settings files created and maintained by the
|
||||||
administrator (and thus trusted) should be placed in
|
administrator (and thus trusted) should be placed in
|
||||||
<filename>/etc/systemd/nspawn/</filename>, while automatically
|
<filename>/etc/systemd/nspawn/</filename>, while automatically
|
||||||
downloaded (and thus potentially untrusted) settings files are
|
downloaded (and thus potentially untrusted) settings files are
|
||||||
|
@ -122,7 +122,7 @@
|
||||||
files acquired from the image vendor, it is recommended to copy the
|
files acquired from the image vendor, it is recommended to copy the
|
||||||
settings files into <filename>/etc/systemd/nspawn/</filename> and
|
settings files into <filename>/etc/systemd/nspawn/</filename> and
|
||||||
edit them there, so that the privileged options become
|
edit them there, so that the privileged options become
|
||||||
available. The precise algorithm how the files are searched and
|
available. The precise algorithm for how the files are searched and
|
||||||
interpreted may be configured with
|
interpreted may be configured with
|
||||||
<command>systemd-nspawn</command>'s <option>--settings=</option>
|
<command>systemd-nspawn</command>'s <option>--settings=</option>
|
||||||
switch, see
|
switch, see
|
||||||
|
@ -141,7 +141,7 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><varname>Boot=</varname></term>
|
<term><varname>Boot=</varname></term>
|
||||||
|
|
||||||
<listitem><para>Takes a boolean argument, defaults to off. If
|
<listitem><para>Takes a boolean argument, which defaults to off. If
|
||||||
enabled, <command>systemd-nspawn</command> will automatically
|
enabled, <command>systemd-nspawn</command> will automatically
|
||||||
search for an <filename>init</filename> executable and invoke
|
search for an <filename>init</filename> executable and invoke
|
||||||
it. In this case, the specified parameters using
|
it. In this case, the specified parameters using
|
||||||
|
@ -240,7 +240,7 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><varname>ReadOnly=</varname></term>
|
<term><varname>ReadOnly=</varname></term>
|
||||||
|
|
||||||
<listitem><para>Takes a boolean argument, defaults to off. If
|
<listitem><para>Takes a boolean argument, which defaults to off. If
|
||||||
specified, the container will be run with a read-only file
|
specified, the container will be run with a read-only file
|
||||||
system. This setting corresponds to the
|
system. This setting corresponds to the
|
||||||
<option>--read-only</option> command line
|
<option>--read-only</option> command line
|
||||||
|
@ -303,7 +303,7 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><varname>Private=</varname></term>
|
<term><varname>Private=</varname></term>
|
||||||
|
|
||||||
<listitem><para>Takes a boolean argument, defaults to off. If
|
<listitem><para>Takes a boolean argument, which defaults to off. If
|
||||||
enabled, the container will run in its own network namespace
|
enabled, the container will run in its own network namespace
|
||||||
and not share network interfaces and configuration with the
|
and not share network interfaces and configuration with the
|
||||||
host. This setting corresponds to the
|
host. This setting corresponds to the
|
||||||
|
@ -315,7 +315,7 @@
|
||||||
<term><varname>VirtualEthernet=</varname></term>
|
<term><varname>VirtualEthernet=</varname></term>
|
||||||
|
|
||||||
<listitem><para>Takes a boolean argument. Configures whether
|
<listitem><para>Takes a boolean argument. Configures whether
|
||||||
to create a virtual ethernet connection
|
to create a virtual Ethernet connection
|
||||||
(<literal>veth</literal>) between host and the container. This
|
(<literal>veth</literal>) between host and the container. This
|
||||||
setting implies <varname>Private=yes</varname>. This setting
|
setting implies <varname>Private=yes</varname>. This setting
|
||||||
corresponds to the <option>--network-veth</option> command
|
corresponds to the <option>--network-veth</option> command
|
||||||
|
|
|
@ -283,7 +283,7 @@
|
||||||
<term><varname>ExecStart=</varname></term>
|
<term><varname>ExecStart=</varname></term>
|
||||||
<listitem><para>Commands with their arguments that are
|
<listitem><para>Commands with their arguments that are
|
||||||
executed when this service is started. The value is split into
|
executed when this service is started. The value is split into
|
||||||
zero or more command lines is according to the rules described
|
zero or more command lines according to the rules described
|
||||||
below (see section "Command Lines" below).
|
below (see section "Command Lines" below).
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
|
@ -343,7 +343,7 @@
|
||||||
|
|
||||||
<para><varname>ExecStartPost=</varname> commands are only run after
|
<para><varname>ExecStartPost=</varname> commands are only run after
|
||||||
the service has started, as determined by <varname>Type=</varname>
|
the service has started, as determined by <varname>Type=</varname>
|
||||||
(i.e. The process has been started for <varname>Type=simple</varname>
|
(i.e. the process has been started for <varname>Type=simple</varname>
|
||||||
or <varname>Type=idle</varname>, the process exits successfully for
|
or <varname>Type=idle</varname>, the process exits successfully for
|
||||||
<varname>Type=oneshot</varname>, the initial process exits successfully
|
<varname>Type=oneshot</varname>, the initial process exits successfully
|
||||||
for <varname>Type=forking</varname>, <literal>READY=1</literal> is sent
|
for <varname>Type=forking</varname>, <literal>READY=1</literal> is sent
|
||||||
|
@ -859,7 +859,7 @@
|
||||||
<option>reboot-immediate</option> causes immediate execution
|
<option>reboot-immediate</option> causes immediate execution
|
||||||
of the
|
of the
|
||||||
<citerefentry><refentrytitle>reboot</refentrytitle><manvolnum>2</manvolnum></citerefentry>
|
<citerefentry><refentrytitle>reboot</refentrytitle><manvolnum>2</manvolnum></citerefentry>
|
||||||
system call, which might result in data loss. Similar,
|
system call, which might result in data loss. Similarly,
|
||||||
<option>poweroff</option>, <option>poweroff-force</option>,
|
<option>poweroff</option>, <option>poweroff-force</option>,
|
||||||
<option>poweroff-immediate</option> have the effect of
|
<option>poweroff-immediate</option> have the effect of
|
||||||
powering down the system with similar semantics. Defaults to
|
powering down the system with similar semantics. Defaults to
|
||||||
|
@ -909,9 +909,9 @@
|
||||||
<ulink
|
<ulink
|
||||||
url="https://www.kernel.org/doc/Documentation/usb/functionfs.txt">USB
|
url="https://www.kernel.org/doc/Documentation/usb/functionfs.txt">USB
|
||||||
FunctionFS</ulink> descriptors, for implementation of USB
|
FunctionFS</ulink> descriptors, for implementation of USB
|
||||||
gadget functions. This is is used only in conjunction with a
|
gadget functions. This is used only in conjunction with a
|
||||||
socket unit with <varname>ListenUSBFunction=</varname>
|
socket unit with <varname>ListenUSBFunction=</varname>
|
||||||
configured. The contents of this file is written to the
|
configured. The contents of this file are written to the
|
||||||
<filename>ep0</filename> file after it is
|
<filename>ep0</filename> file after it is
|
||||||
opened.</para></listitem>
|
opened.</para></listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
@ -1216,7 +1216,7 @@ WantedBy=multi-user.target</programlisting>
|
||||||
then execute another to shut it down, but no process remains
|
then execute another to shut it down, but no process remains
|
||||||
active while they are considered "started". Network
|
active while they are considered "started". Network
|
||||||
configuration can sometimes fall into this category. Another use
|
configuration can sometimes fall into this category. Another use
|
||||||
case is if a oneshot service shall not be executed a each time
|
case is if a oneshot service shall not be executed each time
|
||||||
when they are pulled in as a dependency, but only the first
|
when they are pulled in as a dependency, but only the first
|
||||||
time.</para>
|
time.</para>
|
||||||
|
|
||||||
|
|
|
@ -268,7 +268,7 @@
|
||||||
implementation of USB gadget functions. This expects an
|
implementation of USB gadget functions. This expects an
|
||||||
absolute file system path as the argument. Behavior otherwise
|
absolute file system path as the argument. Behavior otherwise
|
||||||
is very similar to the <varname>ListenFIFO=</varname>
|
is very similar to the <varname>ListenFIFO=</varname>
|
||||||
directive above. Use this to open FunctionFS endpoint
|
directive above. Use this to open the FunctionFS endpoint
|
||||||
<filename>ep0</filename>. When using this option, the
|
<filename>ep0</filename>. When using this option, the
|
||||||
activated service has to have the
|
activated service has to have the
|
||||||
<varname>USBFunctionDescriptors=</varname> and
|
<varname>USBFunctionDescriptors=</varname> and
|
||||||
|
@ -376,7 +376,7 @@
|
||||||
activation.</para>
|
activation.</para>
|
||||||
|
|
||||||
<para>For IPv4 and IPv6 connections, the <varname>REMOTE_ADDR</varname>
|
<para>For IPv4 and IPv6 connections, the <varname>REMOTE_ADDR</varname>
|
||||||
environment variable will contain the remote IP, and <varname>REMOTE_PORT</varname>
|
environment variable will contain the remote IP address, and <varname>REMOTE_PORT</varname>
|
||||||
will contain the remote port. This is the same as the format used by CGI.
|
will contain the remote port. This is the same as the format used by CGI.
|
||||||
For SOCK_RAW, the port is the IP protocol.</para></listitem>
|
For SOCK_RAW, the port is the IP protocol.</para></listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
@ -432,7 +432,7 @@
|
||||||
<term><varname>KeepAliveIntervalSec=</varname></term>
|
<term><varname>KeepAliveIntervalSec=</varname></term>
|
||||||
<listitem><para>Takes time (in seconds) as argument between
|
<listitem><para>Takes time (in seconds) as argument between
|
||||||
individual keepalive probes, if the socket option SO_KEEPALIVE
|
individual keepalive probes, if the socket option SO_KEEPALIVE
|
||||||
has been set on this socket seconds as argument. This controls
|
has been set on this socket. This controls
|
||||||
the TCP_KEEPINTVL socket option (see
|
the TCP_KEEPINTVL socket option (see
|
||||||
<citerefentry project='man-pages'><refentrytitle>socket</refentrytitle><manvolnum>7</manvolnum></citerefentry>
|
<citerefentry project='man-pages'><refentrytitle>socket</refentrytitle><manvolnum>7</manvolnum></citerefentry>
|
||||||
and the <ulink
|
and the <ulink
|
||||||
|
@ -443,7 +443,7 @@
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><varname>KeepAliveProbes=</varname></term>
|
<term><varname>KeepAliveProbes=</varname></term>
|
||||||
<listitem><para>Takes integer as argument. It's the number of
|
<listitem><para>Takes an integer as argument. It's the number of
|
||||||
unacknowledged probes to send before considering the
|
unacknowledged probes to send before considering the
|
||||||
connection dead and notifying the application layer. This
|
connection dead and notifying the application layer. This
|
||||||
controls the TCP_KEEPCNT socket option (see
|
controls the TCP_KEEPCNT socket option (see
|
||||||
|
@ -752,12 +752,12 @@
|
||||||
<term><varname>FileDescriptorName=</varname></term>
|
<term><varname>FileDescriptorName=</varname></term>
|
||||||
<listitem><para>Assigns a name to all file descriptors this
|
<listitem><para>Assigns a name to all file descriptors this
|
||||||
socket unit encapsulates. This is useful to help activated
|
socket unit encapsulates. This is useful to help activated
|
||||||
services to identify specific file descriptors, if multiple
|
services identify specific file descriptors, if multiple fds
|
||||||
are passed. Services may use the
|
are passed. Services may use the
|
||||||
<citerefentry><refentrytitle>sd_listen_fds_with_names</refentrytitle><manvolnum>3</manvolnum></citerefentry>
|
<citerefentry><refentrytitle>sd_listen_fds_with_names</refentrytitle><manvolnum>3</manvolnum></citerefentry>
|
||||||
call to acquire the names configured for the received file
|
call to acquire the names configured for the received file
|
||||||
descriptors. Names may contain any ASCII character, but must
|
descriptors. Names may contain any ASCII character, but must
|
||||||
exclude control characters or <literal>:</literal>, and must
|
exclude control characters and <literal>:</literal>, and must
|
||||||
be at most 255 characters in length. If this setting is not
|
be at most 255 characters in length. If this setting is not
|
||||||
used, the file descriptor name defaults to the name of the
|
used, the file descriptor name defaults to the name of the
|
||||||
socket unit, including its <filename>.socket</filename>
|
socket unit, including its <filename>.socket</filename>
|
||||||
|
|
|
@ -124,7 +124,7 @@
|
||||||
will not be added as a dependency for
|
will not be added as a dependency for
|
||||||
<filename>swap.target</filename>. This means that it will not
|
<filename>swap.target</filename>. This means that it will not
|
||||||
be activated automatically during boot, unless it is pulled in
|
be activated automatically during boot, unless it is pulled in
|
||||||
by some other unit. Option <option>auto</option> has the
|
by some other unit. The <option>auto</option> option has the
|
||||||
opposite meaning and is the default.</para>
|
opposite meaning and is the default.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
@ -177,8 +177,8 @@
|
||||||
|
|
||||||
<listitem><para>Swap priority to use when activating the swap
|
<listitem><para>Swap priority to use when activating the swap
|
||||||
device or file. This takes an integer. This setting is
|
device or file. This takes an integer. This setting is
|
||||||
optional and ignored when priority is set by <option>pri=</option> in the
|
optional and ignored when the priority is set by <option>pri=</option> in the
|
||||||
<varname>Options=</varname> option.</para></listitem>
|
<varname>Options=</varname> key.</para></listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
|
|
|
@ -139,7 +139,7 @@
|
||||||
placeholders instead of timestamps: <literal>now</literal> may be
|
placeholders instead of timestamps: <literal>now</literal> may be
|
||||||
used to refer to the current time (or of the invocation of the
|
used to refer to the current time (or of the invocation of the
|
||||||
command that is currently executed). <literal>today</literal>,
|
command that is currently executed). <literal>today</literal>,
|
||||||
<literal>yesterday</literal>, <literal>tomorrow</literal> refer to
|
<literal>yesterday</literal>, and <literal>tomorrow</literal> refer to
|
||||||
00:00:00 of the current day, the day before, or the next day,
|
00:00:00 of the current day, the day before, or the next day,
|
||||||
respectively.</para>
|
respectively.</para>
|
||||||
|
|
||||||
|
|
|
@ -363,7 +363,7 @@
|
||||||
<refsect1>
|
<refsect1>
|
||||||
<title>[Unit] Section Options</title>
|
<title>[Unit] Section Options</title>
|
||||||
|
|
||||||
<para>Unit file may include a [Unit] section, which carries
|
<para>The unit file may include a [Unit] section, which carries
|
||||||
generic information about the unit that is not dependent on the
|
generic information about the unit that is not dependent on the
|
||||||
type of unit:</para>
|
type of unit:</para>
|
||||||
|
|
||||||
|
@ -1025,7 +1025,7 @@
|
||||||
|
|
||||||
<listitem><para>Similar to the
|
<listitem><para>Similar to the
|
||||||
<varname>ConditionArchitecture=</varname>,
|
<varname>ConditionArchitecture=</varname>,
|
||||||
<varname>ConditionVirtualization=</varname>, ... condition
|
<varname>ConditionVirtualization=</varname>, etc., condition
|
||||||
settings described above, these settings add assertion checks
|
settings described above, these settings add assertion checks
|
||||||
to the start-up of the unit. However, unlike the conditions
|
to the start-up of the unit. However, unlike the conditions
|
||||||
settings, any assertion setting that is not met results in
|
settings, any assertion setting that is not met results in
|
||||||
|
|
|
@ -562,7 +562,7 @@
|
||||||
<filename>ctrl-alt-del.target</filename> unit. This is mostly
|
<filename>ctrl-alt-del.target</filename> unit. This is mostly
|
||||||
equivalent to <command>systemctl start
|
equivalent to <command>systemctl start
|
||||||
ctl-alt-del.target</command>. If this signal is received more
|
ctl-alt-del.target</command>. If this signal is received more
|
||||||
often than 7 times per 2s, an immediate reboot is triggered.
|
than 7 times per 2s, an immediate reboot is triggered.
|
||||||
Note that pressing Ctrl-Alt-Del on the console will trigger
|
Note that pressing Ctrl-Alt-Del on the console will trigger
|
||||||
this signal. Hence, if a reboot is hanging, pressing
|
this signal. Hence, if a reboot is hanging, pressing
|
||||||
Ctrl-Alt-Del more than 7 times in 2s is a relatively safe way
|
Ctrl-Alt-Del more than 7 times in 2s is a relatively safe way
|
||||||
|
|
|
@ -207,7 +207,7 @@ u root 0 "Superuser" /root</programlisting>
|
||||||
|
|
||||||
<para>Note that <command>systemd-sysusers</command> will do
|
<para>Note that <command>systemd-sysusers</command> will do
|
||||||
nothing if the specified users or groups already exist, so
|
nothing if the specified users or groups already exist, so
|
||||||
normally, there no reason to override
|
normally, there is no reason to override
|
||||||
<filename>sysusers.d</filename> vendor configuration, except to
|
<filename>sysusers.d</filename> vendor configuration, except to
|
||||||
block certain users or groups from being created.</para>
|
block certain users or groups from being created.</para>
|
||||||
</refsect1>
|
</refsect1>
|
||||||
|
|
|
@ -387,7 +387,7 @@
|
||||||
<varname>+</varname> (the default one) causes the
|
<varname>+</varname> (the default one) causes the
|
||||||
attribute(s) to be added; <varname>-</varname> causes the
|
attribute(s) to be added; <varname>-</varname> causes the
|
||||||
attribute(s) to be removed; <varname>=</varname> causes the
|
attribute(s) to be removed; <varname>=</varname> causes the
|
||||||
attributes to set exactly as the following letters. The
|
attributes to be set exactly as the following letters. The
|
||||||
letters <literal>aAcCdDeijsStTu</literal> select the new
|
letters <literal>aAcCdDeijsStTu</literal> select the new
|
||||||
attributes for the files, see
|
attributes for the files, see
|
||||||
<citerefentry project='man-pages'><refentrytitle>chattr</refentrytitle>
|
<citerefentry project='man-pages'><refentrytitle>chattr</refentrytitle>
|
||||||
|
@ -414,7 +414,7 @@
|
||||||
<term><varname>a</varname></term>
|
<term><varname>a</varname></term>
|
||||||
<term><varname>a+</varname></term>
|
<term><varname>a+</varname></term>
|
||||||
<listitem><para>Set POSIX ACLs (access control lists). If
|
<listitem><para>Set POSIX ACLs (access control lists). If
|
||||||
suffixed with <varname>+</varname>, specified entries will
|
suffixed with <varname>+</varname>, the specified entries will
|
||||||
be added to the existing set.
|
be added to the existing set.
|
||||||
<command>systemd-tmpfiles</command> will automatically add
|
<command>systemd-tmpfiles</command> will automatically add
|
||||||
the required base entries for user and group based on the
|
the required base entries for user and group based on the
|
||||||
|
@ -537,7 +537,7 @@
|
||||||
<para>The user and group to use for this file or directory. This
|
<para>The user and group to use for this file or directory. This
|
||||||
may either be a numeric user/group ID or a user or group
|
may either be a numeric user/group ID or a user or group
|
||||||
name. If omitted or when set to <literal>-</literal>, the
|
name. If omitted or when set to <literal>-</literal>, the
|
||||||
default 0 (root) is used. For <varname>z</varname>,
|
default 0 (root) is used. For <varname>z</varname> and
|
||||||
<varname>Z</varname> lines, when omitted or when set to
|
<varname>Z</varname> lines, when omitted or when set to
|
||||||
<literal>-</literal>, the file ownership will not be
|
<literal>-</literal>, the file ownership will not be
|
||||||
modified. These parameters are ignored for <varname>x</varname>,
|
modified. These parameters are ignored for <varname>x</varname>,
|
||||||
|
@ -552,16 +552,16 @@
|
||||||
delete when cleaning. If a file or directory is older than the
|
delete when cleaning. If a file or directory is older than the
|
||||||
current time minus the age field, it is deleted. The field
|
current time minus the age field, it is deleted. The field
|
||||||
format is a series of integers each followed by one of the
|
format is a series of integers each followed by one of the
|
||||||
following postfixes for the respective time units:
|
following suffixes for the respective time units:
|
||||||
<constant>s</constant>,
|
<constant>s</constant>,
|
||||||
<constant>m</constant> or <constant>min</constant>,
|
<constant>m</constant> or <constant>min</constant>,
|
||||||
<constant>h</constant>,
|
<constant>h</constant>,
|
||||||
<constant>d</constant>,
|
<constant>d</constant>,
|
||||||
<constant>w</constant>,
|
<constant>w</constant>,
|
||||||
<constant>ms</constant>,
|
<constant>ms</constant>, and
|
||||||
<constant>us</constant>,
|
<constant>us</constant>,
|
||||||
respectively meaning seconds, minutes, hours, days, weeks,
|
meaning seconds, minutes, hours, days, weeks,
|
||||||
milliseconds, and microseconds. Full names of the time units can
|
milliseconds, and microseconds, respectively. Full names of the time units can
|
||||||
be used too.
|
be used too.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
|
@ -590,18 +590,18 @@
|
||||||
<title>Argument</title>
|
<title>Argument</title>
|
||||||
|
|
||||||
<para>For <varname>L</varname> lines determines the destination
|
<para>For <varname>L</varname> lines determines the destination
|
||||||
path of the symlink. For <varname>c</varname>,
|
path of the symlink. For <varname>c</varname> and
|
||||||
<varname>b</varname> determines the major/minor of the device
|
<varname>b</varname>, determines the major/minor of the device
|
||||||
node, with major and minor formatted as integers, separated by
|
node, with major and minor formatted as integers, separated by
|
||||||
<literal>:</literal>, e.g. <literal>1:3</literal>. For
|
<literal>:</literal>, e.g. <literal>1:3</literal>. For
|
||||||
<varname>f</varname>, <varname>F</varname>, and
|
<varname>f</varname>, <varname>F</varname>, and
|
||||||
<varname>w</varname> may be used to specify a short string that
|
<varname>w</varname>, the argument may be used to specify a short string that
|
||||||
is written to the file, suffixed by a newline. For
|
is written to the file, suffixed by a newline. For
|
||||||
<varname>C</varname>, specifies the source file or
|
<varname>C</varname>, specifies the source file or
|
||||||
directory. For <varname>t</varname>, <varname>T</varname>,
|
directory. For <varname>t</varname> and <varname>T</varname>,
|
||||||
determines extended attributes to be set. For
|
determines extended attributes to be set. For
|
||||||
<varname>a</varname>, <varname>A</varname>, determines ACL
|
<varname>a</varname> and <varname>A</varname>, determines ACL
|
||||||
attributes to be set. For <varname>h</varname>,
|
attributes to be set. For <varname>h</varname> and
|
||||||
<varname>H</varname>, determines the file attributes to
|
<varname>H</varname>, determines the file attributes to
|
||||||
set. Ignored for all other lines.</para>
|
set. Ignored for all other lines.</para>
|
||||||
</refsect2>
|
</refsect2>
|
||||||
|
|
|
@ -181,7 +181,7 @@
|
||||||
<function>udev_device_get_parent_with_subsystem_devtype()</function>
|
<function>udev_device_get_parent_with_subsystem_devtype()</function>
|
||||||
return a pointer to the parent device. No additional reference
|
return a pointer to the parent device. No additional reference
|
||||||
to this device is acquired, but the child device owns a reference
|
to this device is acquired, but the child device owns a reference
|
||||||
to such parent device. On failure, <constant>NULL</constant>
|
to such a parent device. On failure, <constant>NULL</constant>
|
||||||
is returned.</para>
|
is returned.</para>
|
||||||
|
|
||||||
<para>On success, <function>udev_device_get_is_initialized()</function>
|
<para>On success, <function>udev_device_get_is_initialized()</function>
|
||||||
|
|
|
@ -141,7 +141,7 @@
|
||||||
and
|
and
|
||||||
<citerefentry><refentrytitle>udev_device_get_sysname</refentrytitle><manvolnum>3</manvolnum></citerefentry>)
|
<citerefentry><refentrytitle>udev_device_get_sysname</refentrytitle><manvolnum>3</manvolnum></citerefentry>)
|
||||||
and <function>udev_device_new_from_device_id</function> looks up devices based on the provided
|
and <function>udev_device_new_from_device_id</function> looks up devices based on the provided
|
||||||
device id, which is a special string in one of the following four forms:
|
device ID, which is a special string in one of the following four forms:
|
||||||
<table>
|
<table>
|
||||||
<title>Device ID strings</title>
|
<title>Device ID strings</title>
|
||||||
|
|
||||||
|
|
|
@ -112,7 +112,7 @@
|
||||||
<constant>NULL</constant> is returned.</para>
|
<constant>NULL</constant> is returned.</para>
|
||||||
|
|
||||||
<para><function>udev_enumerate_get_udev()</function> always
|
<para><function>udev_enumerate_get_udev()</function> always
|
||||||
returns a pointer to the udev context that this enumerate
|
returns a pointer to the udev context that this enumerated
|
||||||
object is associated with.</para>
|
object is associated with.</para>
|
||||||
</refsect1>
|
</refsect1>
|
||||||
|
|
||||||
|
|
|
@ -317,7 +317,7 @@
|
||||||
<term><option>--name-match=<replaceable>NAME</replaceable></option></term>
|
<term><option>--name-match=<replaceable>NAME</replaceable></option></term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Trigger events for devices with a matching
|
<para>Trigger events for devices with a matching
|
||||||
device path. This options can be specified multiple
|
device path. This option can be specified multiple
|
||||||
times.</para>
|
times.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
|
@ -278,7 +278,7 @@ int tlv_packet_parse_pdu(tlv_packet *m, uint16_t size) {
|
||||||
|
|
||||||
p = m->pdu;
|
p = m->pdu;
|
||||||
|
|
||||||
/* extract ethernet header */
|
/* extract Ethernet header */
|
||||||
memcpy(&m->mac, p, ETH_ALEN);
|
memcpy(&m->mac, p, ETH_ALEN);
|
||||||
p += sizeof(struct ether_header);
|
p += sizeof(struct ether_header);
|
||||||
|
|
||||||
|
|
|
@ -1517,7 +1517,7 @@ static int client_receive_message_udp(sd_event_source *s, int fd,
|
||||||
expected_hlen = ETH_ALEN;
|
expected_hlen = ETH_ALEN;
|
||||||
expected_chaddr = (const struct ether_addr *) &client->mac_addr;
|
expected_chaddr = (const struct ether_addr *) &client->mac_addr;
|
||||||
} else {
|
} else {
|
||||||
/* Non-ethernet links expect zero chaddr */
|
/* Non-Ethernet links expect zero chaddr */
|
||||||
expected_hlen = 0;
|
expected_hlen = 0;
|
||||||
expected_chaddr = &zero_mac;
|
expected_chaddr = &zero_mac;
|
||||||
}
|
}
|
||||||
|
|
|
@ -54,7 +54,7 @@ static int lldp_build_tlv_packet(tlv_packet **ret) {
|
||||||
.ether_type = htons(ETHERTYPE_LLDP),
|
.ether_type = htons(ETHERTYPE_LLDP),
|
||||||
};
|
};
|
||||||
|
|
||||||
/* Append ethernet header */
|
/* Append Ethernet header */
|
||||||
memcpy(ðer.ether_dhost, lldp_dst, ETHER_ADDR_LEN);
|
memcpy(ðer.ether_dhost, lldp_dst, ETHER_ADDR_LEN);
|
||||||
memcpy(ðer.ether_shost, &mac_addr, ETHER_ADDR_LEN);
|
memcpy(ðer.ether_shost, &mac_addr, ETHER_ADDR_LEN);
|
||||||
|
|
||||||
|
|
|
@ -209,10 +209,10 @@ static void help(void) {
|
||||||
" --network-ipvlan=INTERFACE\n"
|
" --network-ipvlan=INTERFACE\n"
|
||||||
" Create a ipvlan network interface based on an\n"
|
" Create a ipvlan network interface based on an\n"
|
||||||
" existing network interface to the container\n"
|
" existing network interface to the container\n"
|
||||||
" -n --network-veth Add a virtual ethernet connection between host\n"
|
" -n --network-veth Add a virtual Ethernet connection between host\n"
|
||||||
" and container\n"
|
" and container\n"
|
||||||
" --network-bridge=INTERFACE\n"
|
" --network-bridge=INTERFACE\n"
|
||||||
" Add a virtual ethernet connection between host\n"
|
" Add a virtual Ethernet connection between host\n"
|
||||||
" and container and add it to an existing bridge on\n"
|
" and container and add it to an existing bridge on\n"
|
||||||
" the host\n"
|
" the host\n"
|
||||||
" -p --port=[PROTOCOL:]HOSTPORT[:CONTAINERPORT]\n"
|
" -p --port=[PROTOCOL:]HOSTPORT[:CONTAINERPORT]\n"
|
||||||
|
|
|
@ -378,7 +378,7 @@ int grow_machine_directory(void) {
|
||||||
if (b.f_bavail > b.f_blocks / 3)
|
if (b.f_bavail > b.f_blocks / 3)
|
||||||
return 0;
|
return 0;
|
||||||
|
|
||||||
/* Calculate how much we are willing to add at maximum */
|
/* Calculate how much we are willing to add at most */
|
||||||
max_add = ((uint64_t) a.f_bavail * (uint64_t) a.f_bsize) - VAR_LIB_MACHINES_FREE_MIN;
|
max_add = ((uint64_t) a.f_bavail * (uint64_t) a.f_bsize) - VAR_LIB_MACHINES_FREE_MIN;
|
||||||
|
|
||||||
/* Calculate the old size */
|
/* Calculate the old size */
|
||||||
|
|
|
@ -27,7 +27,7 @@
|
||||||
* http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames
|
* http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames
|
||||||
*
|
*
|
||||||
* Two character prefixes based on the type of interface:
|
* Two character prefixes based on the type of interface:
|
||||||
* en -- ethernet
|
* en -- Ethernet
|
||||||
* sl -- serial line IP (slip)
|
* sl -- serial line IP (slip)
|
||||||
* wl -- wlan
|
* wl -- wlan
|
||||||
* ww -- wwan
|
* ww -- wwan
|
||||||
|
@ -53,17 +53,17 @@
|
||||||
* exported.
|
* exported.
|
||||||
* The usual USB configuration == 1 and interface == 0 values are suppressed.
|
* The usual USB configuration == 1 and interface == 0 values are suppressed.
|
||||||
*
|
*
|
||||||
* PCI ethernet card with firmware index "1":
|
* PCI Ethernet card with firmware index "1":
|
||||||
* ID_NET_NAME_ONBOARD=eno1
|
* ID_NET_NAME_ONBOARD=eno1
|
||||||
* ID_NET_NAME_ONBOARD_LABEL=Ethernet Port 1
|
* ID_NET_NAME_ONBOARD_LABEL=Ethernet Port 1
|
||||||
*
|
*
|
||||||
* PCI ethernet card in hotplug slot with firmware index number:
|
* PCI Ethernet card in hotplug slot with firmware index number:
|
||||||
* /sys/devices/pci0000:00/0000:00:1c.3/0000:05:00.0/net/ens1
|
* /sys/devices/pci0000:00/0000:00:1c.3/0000:05:00.0/net/ens1
|
||||||
* ID_NET_NAME_MAC=enx000000000466
|
* ID_NET_NAME_MAC=enx000000000466
|
||||||
* ID_NET_NAME_PATH=enp5s0
|
* ID_NET_NAME_PATH=enp5s0
|
||||||
* ID_NET_NAME_SLOT=ens1
|
* ID_NET_NAME_SLOT=ens1
|
||||||
*
|
*
|
||||||
* PCI ethernet multi-function card with 2 ports:
|
* PCI Ethernet multi-function card with 2 ports:
|
||||||
* /sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.0/net/enp2s0f0
|
* /sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.0/net/enp2s0f0
|
||||||
* ID_NET_NAME_MAC=enx78e7d1ea46da
|
* ID_NET_NAME_MAC=enx78e7d1ea46da
|
||||||
* ID_NET_NAME_PATH=enp2s0f0
|
* ID_NET_NAME_PATH=enp2s0f0
|
||||||
|
|
Loading…
Reference in New Issue