2010-07-07 07:38:56 +08:00
|
|
|
<?xml version='1.0'?> <!--*-nxml-*-->
|
|
|
|
|
<?xml-stylesheet type="text/xsl" href="http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl"?>
|
|
|
|
|
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
|
|
|
|
|
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
|
|
|
|
|
|
|
|
|
|
<!--
|
|
|
|
|
This file is part of systemd.
|
|
|
|
|
|
|
|
|
|
Copyright 2010 Lennart Poettering
|
|
|
|
|
|
|
|
|
|
systemd is free software; you can redistribute it and/or modify it
|
2012-04-12 06:20:58 +08:00
|
|
|
under the terms of the GNU Lesser General Public License as published by
|
|
|
|
|
the Free Software Foundation; either version 2.1 of the License, or
|
2010-07-07 07:38:56 +08:00
|
|
|
(at your option) any later version.
|
|
|
|
|
|
|
|
|
|
systemd is distributed in the hope that it will be useful, but
|
|
|
|
|
WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
2012-04-12 06:20:58 +08:00
|
|
|
Lesser General Public License for more details.
|
2010-07-07 07:38:56 +08:00
|
|
|
|
2012-04-12 06:20:58 +08:00
|
|
|
You should have received a copy of the GNU Lesser General Public License
|
2010-07-07 07:38:56 +08:00
|
|
|
along with systemd; If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
|
-->
|
|
|
|
|
|
2013-02-12 03:42:24 +08:00
|
|
|
<refentry id="systemd-system.conf">
|
2010-07-07 07:38:56 +08:00
|
|
|
<refentryinfo>
|
2013-02-12 03:42:24 +08:00
|
|
|
<title>systemd-system.conf</title>
|
2010-07-07 07:38:56 +08:00
|
|
|
<productname>systemd</productname>
|
|
|
|
|
|
|
|
|
|
<authorgroup>
|
|
|
|
|
<author>
|
|
|
|
|
<contrib>Developer</contrib>
|
|
|
|
|
<firstname>Lennart</firstname>
|
|
|
|
|
<surname>Poettering</surname>
|
|
|
|
|
<email>lennart@poettering.net</email>
|
|
|
|
|
</author>
|
|
|
|
|
</authorgroup>
|
|
|
|
|
</refentryinfo>
|
|
|
|
|
|
|
|
|
|
<refmeta>
|
2013-02-12 03:42:24 +08:00
|
|
|
<refentrytitle>systemd-system.conf</refentrytitle>
|
2010-07-07 07:38:56 +08:00
|
|
|
<manvolnum>5</manvolnum>
|
|
|
|
|
</refmeta>
|
|
|
|
|
|
|
|
|
|
<refnamediv>
|
2013-02-12 03:42:24 +08:00
|
|
|
<refname>systemd-system.conf</refname>
|
|
|
|
|
<refname>systemd-user.conf</refname>
|
|
|
|
|
<refpurpose>System and session service manager configuration file</refpurpose>
|
2010-07-07 07:38:56 +08:00
|
|
|
</refnamediv>
|
|
|
|
|
|
|
|
|
|
<refsynopsisdiv>
|
2012-06-25 18:00:43 +08:00
|
|
|
<para><filename>/etc/systemd/system.conf</filename></para>
|
|
|
|
|
<para><filename>/etc/systemd/user.conf</filename></para>
|
2010-07-07 07:38:56 +08:00
|
|
|
</refsynopsisdiv>
|
|
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
|
<title>Description</title>
|
|
|
|
|
|
|
|
|
|
<para>When run as system instance systemd reads the
|
|
|
|
|
configuration file <filename>system.conf</filename>,
|
2010-11-16 05:12:41 +08:00
|
|
|
otherwise <filename>user.conf</filename>. These
|
2010-07-07 07:38:56 +08:00
|
|
|
configuration files contain a few settings controlling
|
|
|
|
|
basic manager operations.</para>
|
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
|
<title>Options</title>
|
|
|
|
|
|
|
|
|
|
<para>All options are configured in the
|
|
|
|
|
<literal>[Manager]</literal> section:</para>
|
|
|
|
|
|
2012-08-11 01:14:30 +08:00
|
|
|
<variablelist class='systemd-directives'>
|
2010-07-07 07:38:56 +08:00
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>LogLevel=</varname></term>
|
|
|
|
|
<term><varname>LogTarget=</varname></term>
|
|
|
|
|
<term><varname>LogColor=</varname></term>
|
|
|
|
|
<term><varname>LogLocation=</varname></term>
|
|
|
|
|
<term><varname>DumpCore=yes</varname></term>
|
|
|
|
|
<term><varname>CrashShell=no</varname></term>
|
|
|
|
|
<term><varname>ShowStatus=yes</varname></term>
|
|
|
|
|
<term><varname>CrashChVT=1</varname></term>
|
2012-01-06 06:54:45 +08:00
|
|
|
<term><varname>DefaultStandardOutput=journal</varname></term>
|
2011-02-15 18:52:29 +08:00
|
|
|
<term><varname>DefaultStandardError=inherit</varname></term>
|
2010-07-07 07:38:56 +08:00
|
|
|
|
|
|
|
|
<listitem><para>Configures various
|
|
|
|
|
parameters of basic manager
|
|
|
|
|
operation. These options may be
|
2010-12-31 08:50:51 +08:00
|
|
|
overridden by the respective command
|
2010-07-07 07:38:56 +08:00
|
|
|
line arguments. See
|
|
|
|
|
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>
|
|
|
|
|
for details about these command line
|
|
|
|
|
arguments.</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>CPUAffinity=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Configures the initial
|
|
|
|
|
CPU affinity for the init
|
2010-09-03 22:30:48 +08:00
|
|
|
process. Takes a space-separated list
|
2014-02-17 10:37:18 +08:00
|
|
|
of CPU indices.</para></listitem>
|
2010-11-16 05:12:41 +08:00
|
|
|
</varlistentry>
|
2010-11-18 07:42:35 +08:00
|
|
|
|
|
|
|
|
<varlistentry>
|
2013-09-27 04:49:44 +08:00
|
|
|
<term><varname>JoinControllers=cpu,cpuacct net_cls,netprio</varname></term>
|
2011-08-23 06:37:35 +08:00
|
|
|
|
|
|
|
|
<listitem><para>Configures controllers
|
|
|
|
|
that shall be mounted in a single
|
2013-09-13 03:12:49 +08:00
|
|
|
hierarchy. By default, systemd will
|
2011-08-23 06:37:35 +08:00
|
|
|
mount all controllers which are
|
|
|
|
|
enabled in the kernel in individual
|
2012-07-15 16:41:40 +08:00
|
|
|
hierarchies, with the exception of
|
2011-08-23 06:37:35 +08:00
|
|
|
those listed in this setting. Takes a
|
2013-06-28 03:51:44 +08:00
|
|
|
space-separated list of comma-separated
|
|
|
|
|
controller names, in order
|
2011-08-23 06:37:35 +08:00
|
|
|
to allow multiple joined
|
|
|
|
|
hierarchies. Defaults to
|
|
|
|
|
'cpu,cpuacct'. Pass an empty string to
|
|
|
|
|
ensure that systemd mounts all
|
|
|
|
|
controllers in separate
|
2013-01-15 03:37:12 +08:00
|
|
|
hierarchies.</para>
|
|
|
|
|
|
|
|
|
|
<para>Note that this option is only
|
|
|
|
|
applied once, at very early boot. If
|
|
|
|
|
you use an initial RAM disk (initrd)
|
2013-06-28 03:51:44 +08:00
|
|
|
that uses systemd, it might hence be
|
2013-01-15 03:37:12 +08:00
|
|
|
necessary to rebuild the initrd if
|
|
|
|
|
this option is changed, and make sure
|
|
|
|
|
the new configuration file is included
|
2013-09-13 03:12:49 +08:00
|
|
|
in it. Otherwise, the initrd might
|
2013-04-15 10:37:54 +08:00
|
|
|
mount the controller hierarchies in a
|
2013-01-16 01:17:53 +08:00
|
|
|
different configuration than intended,
|
|
|
|
|
and the main system cannot remount
|
|
|
|
|
them anymore.</para></listitem>
|
2011-08-23 06:37:35 +08:00
|
|
|
</varlistentry>
|
2012-04-06 04:08:10 +08:00
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>RuntimeWatchdogSec=</varname></term>
|
|
|
|
|
<term><varname>ShutdownWatchdogSec=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Configure the hardware
|
|
|
|
|
watchdog at runtime and at
|
|
|
|
|
reboot. Takes a timeout value in
|
|
|
|
|
seconds (or in other time units if
|
|
|
|
|
suffixed with <literal>ms</literal>,
|
|
|
|
|
<literal>min</literal>,
|
|
|
|
|
<literal>h</literal>,
|
|
|
|
|
<literal>d</literal>,
|
|
|
|
|
<literal>w</literal>). If
|
|
|
|
|
<varname>RuntimeWatchdogSec=</varname>
|
2013-09-13 03:12:49 +08:00
|
|
|
is set to a non-zero value, the
|
2012-04-06 04:08:10 +08:00
|
|
|
watchdog hardware
|
|
|
|
|
(<filename>/dev/watchdog</filename>)
|
|
|
|
|
will be programmed to automatically
|
|
|
|
|
reboot the system if it is not
|
|
|
|
|
contacted within the specified timeout
|
|
|
|
|
interval. The system manager will
|
|
|
|
|
ensure to contact it at least once in
|
|
|
|
|
half the specified timeout
|
|
|
|
|
interval. This feature requires a
|
|
|
|
|
hardware watchdog device to be
|
|
|
|
|
present, as it is commonly the case in
|
|
|
|
|
embedded and server systems. Not all
|
|
|
|
|
hardware watchdogs allow configuration
|
|
|
|
|
of the reboot timeout, in which case
|
|
|
|
|
the closest available timeout is
|
|
|
|
|
picked. <varname>ShutdownWatchdogSec=</varname>
|
|
|
|
|
may be used to configure the hardware
|
|
|
|
|
watchdog when the system is asked to
|
|
|
|
|
reboot. It works as a safety net to
|
|
|
|
|
ensure that the reboot takes place
|
|
|
|
|
even if a clean reboot attempt times
|
|
|
|
|
out. By default
|
|
|
|
|
<varname>RuntimeWatchdogSec=</varname>
|
|
|
|
|
defaults to 0 (off), and
|
|
|
|
|
<varname>ShutdownWatchdogSec=</varname>
|
|
|
|
|
to 10min. These settings have no
|
|
|
|
|
effect if a hardware watchdog is not
|
|
|
|
|
available.</para></listitem>
|
|
|
|
|
</varlistentry>
|
2012-03-22 01:03:40 +08:00
|
|
|
|
2012-05-24 10:00:56 +08:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>CapabilityBoundingSet=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Controls which
|
|
|
|
|
capabilities to include in the
|
|
|
|
|
capability bounding set for PID 1 and
|
|
|
|
|
its children. See
|
|
|
|
|
<citerefentry><refentrytitle>capabilities</refentrytitle><manvolnum>7</manvolnum></citerefentry>
|
2013-06-28 03:51:44 +08:00
|
|
|
for details. Takes a whitespace-separated
|
|
|
|
|
list of capability names as read by
|
2012-05-24 10:00:56 +08:00
|
|
|
<citerefentry><refentrytitle>cap_from_name</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
|
|
|
|
|
Capabilities listed will be included
|
|
|
|
|
in the bounding set, all others are
|
|
|
|
|
removed. If the list of capabilities
|
2013-09-13 03:12:49 +08:00
|
|
|
is prefixed with ~, all but the listed
|
2012-05-24 10:00:56 +08:00
|
|
|
capabilities will be included, the
|
|
|
|
|
effect of the assignment
|
|
|
|
|
inverted. Note that this option also
|
2012-10-26 06:16:47 +08:00
|
|
|
affects the respective capabilities in
|
2012-05-24 10:00:56 +08:00
|
|
|
the effective, permitted and
|
|
|
|
|
inheritable capability sets. The
|
|
|
|
|
capability bounding set may also be
|
|
|
|
|
individually configured for units
|
|
|
|
|
using the
|
|
|
|
|
<varname>CapabilityBoundingSet=</varname>
|
|
|
|
|
directive for units, but note that
|
|
|
|
|
capabilities dropped for PID 1 cannot
|
|
|
|
|
be regained in individual units, they
|
|
|
|
|
are lost for good.</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2014-02-13 08:35:27 +08:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>SystemCallArchitectures=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Takes a
|
|
|
|
|
space-separated list of architecture
|
2014-02-17 10:37:18 +08:00
|
|
|
identifiers. Selects from which
|
2014-02-13 08:35:27 +08:00
|
|
|
architectures system calls may be
|
|
|
|
|
invoked on this system. This may be
|
|
|
|
|
used as an effective way to disable
|
|
|
|
|
invocation of non-native binaries
|
|
|
|
|
system-wide, for example to prohibit
|
2014-02-17 10:37:13 +08:00
|
|
|
execution of 32-bit x86 binaries on
|
|
|
|
|
64-bit x86-64 systems. This option
|
|
|
|
|
operates system-wide, and acts
|
2014-02-13 08:35:27 +08:00
|
|
|
similar to the
|
|
|
|
|
<varname>SystemCallArchitectures=</varname>
|
|
|
|
|
setting of unit files, see
|
|
|
|
|
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
|
|
|
|
for details. This setting defaults to
|
2014-02-17 10:37:13 +08:00
|
|
|
the empty list, in which case no
|
2014-02-13 08:35:27 +08:00
|
|
|
filtering of system calls based on
|
|
|
|
|
architecture is applied. Known
|
|
|
|
|
architecture identifiers are
|
|
|
|
|
<literal>x86</literal>,
|
|
|
|
|
<literal>x86-64</literal>,
|
|
|
|
|
<literal>x32</literal>,
|
|
|
|
|
<literal>arm</literal> and the special
|
|
|
|
|
identifier
|
|
|
|
|
<literal>native</literal>. The latter
|
|
|
|
|
implicitly maps to the native
|
|
|
|
|
architecture of the system (or more
|
|
|
|
|
specifically, the architecture the
|
|
|
|
|
system manager was compiled for). Set
|
|
|
|
|
this setting to
|
|
|
|
|
<literal>native</literal> to prohibit
|
|
|
|
|
execution of any non-native
|
|
|
|
|
binaries. When a binary executes a
|
|
|
|
|
system call of an architecture that is
|
2014-02-17 10:37:13 +08:00
|
|
|
not listed in this setting, it will be
|
2014-02-13 08:35:27 +08:00
|
|
|
immediately terminated with the SIGSYS
|
|
|
|
|
signal.</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
|
2012-05-31 10:36:08 +08:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>TimerSlackNSec=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Sets the timer slack
|
2014-03-24 23:22:34 +08:00
|
|
|
in nanoseconds for PID 1, which is
|
|
|
|
|
inherited by all executed processes,
|
2012-10-26 06:16:47 +08:00
|
|
|
unless overridden individually, for
|
2012-05-31 10:36:08 +08:00
|
|
|
example with the
|
|
|
|
|
<varname>TimerSlackNSec=</varname>
|
|
|
|
|
setting in service units (for details
|
|
|
|
|
see
|
|
|
|
|
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>). The
|
|
|
|
|
timer slack controls the accuracy of
|
2014-03-24 23:22:34 +08:00
|
|
|
wake-ups triggered by system
|
|
|
|
|
timers. See
|
2012-05-31 10:36:08 +08:00
|
|
|
<citerefentry><refentrytitle>prctl</refentrytitle><manvolnum>2</manvolnum></citerefentry>
|
|
|
|
|
for more information. Note that in
|
|
|
|
|
contrast to most other time span
|
|
|
|
|
definitions this parameter takes an
|
|
|
|
|
integer value in nano-seconds if no
|
|
|
|
|
unit is specified. The usual time
|
|
|
|
|
units are understood
|
|
|
|
|
too.</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2014-03-24 23:22:34 +08:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>DefaultTimerAccuracySec=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Sets the default
|
|
|
|
|
accuracy of timer units. This controls
|
|
|
|
|
the global default for the
|
|
|
|
|
<varname>AccuracySec=</varname>
|
|
|
|
|
setting of timer units, see
|
|
|
|
|
<citerefentry><refentrytitle>systemd.timer</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
|
|
|
|
for
|
|
|
|
|
details. <varname>AccuracySec=</varname>
|
|
|
|
|
set in individual units override the
|
|
|
|
|
global default for the specific
|
|
|
|
|
unit. Defaults to 1min. Note that the
|
|
|
|
|
accuracy of timer units is also
|
|
|
|
|
affected by the configured timer slack
|
|
|
|
|
for PID 1, see
|
|
|
|
|
<varname>TimerSlackNSec=</varname>
|
|
|
|
|
above.</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2014-04-25 19:27:25 +08:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>DefaultCPUQuotaPeriodSec=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Sets the default CPU
|
|
|
|
|
quota period. Defaults to 100ms. This
|
|
|
|
|
controls th global default for the
|
|
|
|
|
<varname>CPUQuotaPeriodSec=</varname>
|
|
|
|
|
setting of units, see
|
|
|
|
|
<citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
|
|
|
|
for details.</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2014-02-13 08:35:27 +08:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>DefaultTimeoutStartSec=</varname></term>
|
|
|
|
|
<term><varname>DefaultTimeoutStopSec=</varname></term>
|
|
|
|
|
<term><varname>DefaultRestartSec=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Configures the default
|
2014-02-17 10:37:13 +08:00
|
|
|
timeouts for starting and stopping of
|
2014-02-13 08:35:27 +08:00
|
|
|
units, as well as the default time to
|
|
|
|
|
sleep between automatic restarts of
|
|
|
|
|
units, as configured per-unit in
|
|
|
|
|
<varname>TimeoutStartSec=</varname>,
|
|
|
|
|
<varname>TimeoutStopSec=</varname> and
|
|
|
|
|
<varname>RestartSec=</varname> (for
|
2014-02-25 06:50:10 +08:00
|
|
|
services, see
|
2014-02-13 08:35:27 +08:00
|
|
|
<citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
|
|
|
|
for details on the per-unit
|
|
|
|
|
settings). For non-service units,
|
|
|
|
|
<varname>DefaultTimeoutStartSec=</varname>
|
|
|
|
|
sets the default
|
|
|
|
|
<varname>TimeoutSec=</varname> value.
|
|
|
|
|
</para></listitem>
|
|
|
|
|
</varlistentry>
|
2014-02-25 06:50:10 +08:00
|
|
|
|
2014-02-13 08:35:27 +08:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>DefaultStartLimitInterval=</varname></term>
|
|
|
|
|
<term><varname>DefaultStartLimitBurst=</varname></term>
|
|
|
|
|
|
2014-02-25 06:50:10 +08:00
|
|
|
<listitem><para>Configure the default
|
|
|
|
|
unit start rate limiting, as
|
|
|
|
|
configured per-service by
|
|
|
|
|
<varname>StartLimitInterval=</varname>
|
|
|
|
|
and
|
2014-02-13 08:35:27 +08:00
|
|
|
<varname>StartLimitBurst=</varname>. See
|
|
|
|
|
<citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
|
|
|
|
for details on the per-service
|
2014-02-25 06:50:10 +08:00
|
|
|
settings.</para></listitem>
|
2014-02-13 08:35:27 +08:00
|
|
|
</varlistentry>
|
|
|
|
|
|
2013-06-09 13:08:46 +08:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>DefaultEnvironment=</varname></term>
|
|
|
|
|
|
2013-06-21 05:31:21 +08:00
|
|
|
<listitem><para>Sets manager
|
|
|
|
|
environment variables passed to all
|
|
|
|
|
executed processes. Takes a
|
|
|
|
|
space-separated list of variable
|
|
|
|
|
assignments. See
|
|
|
|
|
<citerefentry><refentrytitle>environ</refentrytitle><manvolnum>7</manvolnum></citerefentry>
|
|
|
|
|
for details about environment
|
|
|
|
|
variables.</para>
|
2013-06-09 13:08:46 +08:00
|
|
|
|
|
|
|
|
<para>Example:
|
|
|
|
|
|
2013-06-21 05:31:21 +08:00
|
|
|
<programlisting>DefaultEnvironment="VAR1=word1 word2" VAR2=word3 "VAR3=word 5 6"</programlisting>
|
|
|
|
|
|
|
|
|
|
Sets three variables
|
|
|
|
|
<literal>VAR1</literal>,
|
|
|
|
|
<literal>VAR2</literal>,
|
|
|
|
|
<literal>VAR3</literal>.</para></listitem>
|
2013-06-09 13:08:46 +08:00
|
|
|
</varlistentry>
|
|
|
|
|
|
2014-02-25 06:50:10 +08:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>DefaultCPUAccounting=</varname></term>
|
|
|
|
|
<term><varname>DefaultBlockIOAccounting=</varname></term>
|
|
|
|
|
<term><varname>DefaultMemoryAccounting=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Configure the default
|
|
|
|
|
resource accounting settings, as
|
|
|
|
|
configured per-unit by
|
|
|
|
|
<varname>CPUAccounting=</varname>,
|
|
|
|
|
<varname>BlockIOAccounting=</varname>
|
|
|
|
|
and
|
|
|
|
|
<varname>MemoryAccounting=</varname>. See
|
|
|
|
|
<citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
|
|
|
|
for details on the per-unit
|
|
|
|
|
settings.</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2012-03-22 01:03:40 +08:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>DefaultLimitCPU=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitFSIZE=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitDATA=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitSTACK=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitCORE=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitRSS=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitNOFILE=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitAS=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitNPROC=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitMEMLOCK=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitLOCKS=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitSIGPENDING=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitMSGQUEUE=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitNICE=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitRTPRIO=</varname></term>
|
|
|
|
|
<term><varname>DefaultLimitRTTIME=</varname></term>
|
2012-05-24 10:00:56 +08:00
|
|
|
|
2012-03-22 01:03:40 +08:00
|
|
|
<listitem><para>These settings control
|
2012-05-24 10:00:56 +08:00
|
|
|
various default resource limits for
|
|
|
|
|
units. See
|
2012-03-22 01:03:40 +08:00
|
|
|
<citerefentry><refentrytitle>setrlimit</refentrytitle><manvolnum>2</manvolnum></citerefentry>
|
|
|
|
|
for details. Use the string
|
|
|
|
|
<varname>infinity</varname> to
|
|
|
|
|
configure no limit on a specific
|
2012-05-24 10:00:56 +08:00
|
|
|
resource. These settings may be
|
2012-10-26 06:16:47 +08:00
|
|
|
overridden in individual units
|
2012-05-24 10:00:56 +08:00
|
|
|
using the corresponding LimitXXX=
|
|
|
|
|
directives. Note that these resource
|
|
|
|
|
limits are only defaults for units,
|
|
|
|
|
they are not applied to PID 1
|
|
|
|
|
itself.</para></listitem>
|
2012-03-22 01:03:40 +08:00
|
|
|
</varlistentry>
|
2010-07-07 07:38:56 +08:00
|
|
|
</variablelist>
|
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
|
<title>See Also</title>
|
|
|
|
|
<para>
|
2013-01-15 11:08:33 +08:00
|
|
|
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
|
2013-06-21 05:31:21 +08:00
|
|
|
<citerefentry><refentrytitle>systemd.directives</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
|
2014-02-13 08:35:27 +08:00
|
|
|
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
|
|
|
|
|
<citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
|
|
|
|
|
<citerefentry><refentrytitle>environ</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
|
|
|
|
|
<citerefentry><refentrytitle>capabilities</refentrytitle><manvolnum>7</manvolnum></citerefentry>
|
2010-07-07 07:38:56 +08:00
|
|
|
</para>
|
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
|
|
</refentry>
|
