parent
ab1f7245c9
commit
98e9d71022
|
@ -12,8 +12,8 @@
|
|||
<listitem><para>Pager to use when <option>--no-pager</option> is not given; overrides
|
||||
<varname>$PAGER</varname>. If neither <varname>$SYSTEMD_PAGER</varname> nor <varname>$PAGER</varname> are set, a
|
||||
set of well-known pager implementations are tried in turn, including
|
||||
<citerefentry><refentrytitle>less</refentrytitle><manvolnum>1</manvolnum></citerefentry> and
|
||||
<citerefentry><refentrytitle>more</refentrytitle><manvolnum>1</manvolnum></citerefentry>, until one is found. If
|
||||
<citerefentry project='man-pages'><refentrytitle>less</refentrytitle><manvolnum>1</manvolnum></citerefentry> and
|
||||
<citerefentry project='man-pages'><refentrytitle>more</refentrytitle><manvolnum>1</manvolnum></citerefentry>, until one is found. If
|
||||
no pager implementation is discovered no pager is invoked. Setting this environment variable to an empty string
|
||||
or the value <literal>cat</literal> is equivalent to passing <option>--no-pager</option>.</para></listitem>
|
||||
</varlistentry>
|
||||
|
|
|
@ -123,7 +123,7 @@
|
|||
|
||||
<para>In order to by used in the <option>--backtrace</option> mode, an appropriate backtrace
|
||||
handler must be installed on the sender side. For example, in case of
|
||||
<citerefentry><refentrytitle>python</refentrytitle><manvolnum>1</manvolnum></citerefentry>, this
|
||||
<citerefentry project='die-net'><refentrytitle>python</refentrytitle><manvolnum>1</manvolnum></citerefentry>, this
|
||||
means a <varname>sys.excepthook</varname> must installed, see
|
||||
<ulink url="https://github.com/keszybz/systemd-coredump-python">systemd-coredump-python</ulink>.
|
||||
</para>
|
||||
|
|
|
@ -76,7 +76,7 @@
|
|||
<replaceable>WHERE</replaceable>.</para>
|
||||
|
||||
<para>In many ways, <command>systemd-mount</command> is similar to the lower-level
|
||||
<citerefentry><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry> command, however instead
|
||||
<citerefentry project='man-pages'><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry> command, however instead
|
||||
of executing the mount operation directly and immediately, <command>systemd-mount</command> schedules it through
|
||||
the service manager job queue, so that it may pull in further dependencies (such as parent mounts, or a file system
|
||||
checker to execute a priori), and may make use of the auto-mounting logic.</para>
|
||||
|
@ -301,7 +301,7 @@
|
|||
<title>See Also</title>
|
||||
<para>
|
||||
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
|
||||
<citerefentry><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
||||
<citerefentry project='man-pages'><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
||||
<citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
|
||||
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
|
||||
<citerefentry><refentrytitle>systemd.mount</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
|
||||
|
|
|
@ -1580,7 +1580,7 @@
|
|||
|
||||
<listitem><para>Restricts access to Linux namespace functionality for the processes of this unit. For details
|
||||
about Linux namespaces, see
|
||||
<citerefentry><refentrytitle>namespaces</refentrytitle><manvolnum>7</manvolnum></citerefentry>. Either takes a
|
||||
<citerefentry project='man-pages'><refentrytitle>namespaces</refentrytitle><manvolnum>7</manvolnum></citerefentry>. Either takes a
|
||||
boolean argument, or a space-separated list of namespace type identifiers. If false (the default), no
|
||||
restrictions on namespace creation and switching are made. If true, access to any kind of namespacing is
|
||||
prohibited. Otherwise, a space-separated list of namespace type identifiers must be specified, consisting of
|
||||
|
|
|
@ -230,7 +230,7 @@
|
|||
<listitem><para>The block device backed file system will be upgraded
|
||||
to <varname>BindsTo=</varname> dependency. This option is only useful
|
||||
when mounting file systems manually with
|
||||
<citerefentry><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry>
|
||||
<citerefentry project='man-pages'><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry>
|
||||
as the default dependency in this case is <varname>Requires=</varname>.
|
||||
This option is already implied by entries in <filename>/etc/fstab</filename>
|
||||
or by mount units.
|
||||
|
|
|
@ -507,7 +507,7 @@
|
|||
<para>This setting is read by
|
||||
<citerefentry><refentrytitle>systemd-resolved.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
|
||||
"Search domains" correspond to the <varname>domain</varname> and <varname>search</varname> entries in
|
||||
<citerefentry><refentrytitle>resolv.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
|
||||
<citerefentry project='man-pages'><refentrytitle>resolv.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
|
||||
Domain name routing has no equivalent in the traditional glibc API, which has no concept of domain
|
||||
name servers limited to a specific link.</para>
|
||||
</listitem>
|
||||
|
|
Loading…
Reference in New Issue