2010-07-07 03:38:56 +04: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 02:20:58 +04: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 03:38:56 +04: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 02:20:58 +04:00
Lesser General Public License for more details.
2010-07-07 03:38:56 +04:00
2012-04-12 02:20:58 +04:00
You should have received a copy of the GNU Lesser General Public License
2010-07-07 03:38:56 +04:00
along with systemd; If not, see <http: / / w w w . g n u . o r g / l i c e n s e s /> .
-->
2013-02-11 23:42:24 +04:00
<refentry id= "systemd-system.conf" >
2010-07-07 03:38:56 +04:00
<refentryinfo >
2013-02-11 23:42:24 +04:00
<title > systemd-system.conf</title>
2010-07-07 03:38:56 +04: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-11 23:42:24 +04:00
<refentrytitle > systemd-system.conf</refentrytitle>
2010-07-07 03:38:56 +04:00
<manvolnum > 5</manvolnum>
</refmeta>
<refnamediv >
2013-02-11 23:42:24 +04:00
<refname > systemd-system.conf</refname>
<refname > systemd-user.conf</refname>
<refpurpose > System and session service manager configuration file</refpurpose>
2010-07-07 03:38:56 +04:00
</refnamediv>
<refsynopsisdiv >
2012-06-25 14:00:43 +04:00
<para > <filename > /etc/systemd/system.conf</filename> </para>
<para > <filename > /etc/systemd/user.conf</filename> </para>
2010-07-07 03:38:56 +04:00
</refsynopsisdiv>
<refsect1 >
<title > Description</title>
<para > When run as system instance systemd reads the
configuration file <filename > system.conf</filename> ,
2010-11-16 00:12:41 +03:00
otherwise <filename > user.conf</filename> . These
2010-07-07 03:38:56 +04: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-10 21:14:30 +04:00
<variablelist class= 'systemd-directives' >
2010-07-07 03:38:56 +04: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 02:54:45 +04:00
<term > <varname > DefaultStandardOutput=journal</varname> </term>
2011-02-15 13:52:29 +03:00
<term > <varname > DefaultStandardError=inherit</varname> </term>
2010-07-07 03:38:56 +04:00
<listitem > <para > Configures various
parameters of basic manager
operation. These options may be
2010-12-31 03:50:51 +03:00
overridden by the respective command
2010-07-07 03:38:56 +04: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 18:30:48 +04:00
process. Takes a space-separated list
2010-07-07 03:38:56 +04:00
of CPU indexes.</para> </listitem>
2010-11-16 00:12:41 +03:00
</varlistentry>
2010-11-18 02:42:35 +03:00
<varlistentry >
<term > <varname > DefaultControllers=cpu</varname> </term>
<listitem > <para > Configures in which
2013-02-27 18:00:26 +04:00
control group hierarchies to create
per-service cgroups automatically, in
addition to the
<literal > name=systemd</literal> named
hierarchy. Defaults to
<literal > cpu</literal> . Takes a space
separated list of controller
names. Pass the empty string to ensure
that systemd does not touch any
hierarchies but its own.</para>
2013-01-15 21:17:53 +04:00
<para > Note that the default value of
'cpu' will make realtime scheduling
unavailable to system services. See
<ulink
url="http://www.freedesktop.org/wiki/Software/systemd/MyServiceCantGetRealtime">My
Service Can't Get Realtime!</ulink>
for more
information.</para> </listitem>
2010-11-18 02:42:35 +03:00
</varlistentry>
2011-08-23 02:37:35 +04:00
<varlistentry >
2012-09-04 05:54:32 +04:00
<term > <varname > JoinControllers=cpu,cpuacct,cpuset net_cls,netprio</varname> </term>
2011-08-23 02:37:35 +04:00
<listitem > <para > Configures controllers
that shall be mounted in a single
hierarchy. By default systemd will
mount all controllers which are
enabled in the kernel in individual
2012-07-15 12:41:40 +04:00
hierarchies, with the exception of
2011-08-23 02:37:35 +04:00
those listed in this setting. Takes a
space separated list of comma
separated controller names, in order
to allow multiple joined
hierarchies. Defaults to
'cpu,cpuacct'. Pass an empty string to
ensure that systemd mounts all
controllers in separate
2013-01-14 23:37:12 +04:00
hierarchies.</para>
<para > Note that this option is only
applied once, at very early boot. If
you use an initial RAM disk (initrd)
that uses systemd it might hence be
necessary to rebuild the initrd if
this option is changed, and make sure
the new configuration file is included
in it. Otherwise the initrd might
2013-01-15 21:17:53 +04:00
mount the controller hierachies in a
different configuration than intended,
and the main system cannot remount
them anymore.</para> </listitem>
2011-08-23 02:37:35 +04:00
</varlistentry>
2012-04-06 00:08:10 +04: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>
is set to a non-zero value the
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-21 21:03:40 +04:00
2012-05-24 06:00:56 +04: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>
for details. Takes a whitespace
separated list of capability names as
read by
<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
is prefixed with ~ all but the listed
capabilities will be included, the
effect of the assignment
inverted. Note that this option also
2012-10-26 02:16:47 +04:00
affects the respective capabilities in
2012-05-24 06:00:56 +04: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>
2012-05-31 06:36:08 +04:00
<varlistentry >
<term > <varname > TimerSlackNSec=</varname> </term>
<listitem > <para > Sets the timer slack
in nanoseconds for PID 1 which is then
inherited to all executed processes,
2012-10-26 02:16:47 +04:00
unless overridden individually, for
2012-05-31 06:36:08 +04: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
wake-ups triggered by timers. See
<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>
2012-03-21 21:03:40 +04: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 06:00:56 +04:00
2012-03-21 21:03:40 +04:00
<listitem > <para > These settings control
2012-05-24 06:00:56 +04:00
various default resource limits for
units. See
2012-03-21 21:03:40 +04: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 06:00:56 +04:00
resource. These settings may be
2012-10-26 02:16:47 +04:00
overridden in individual units
2012-05-24 06:00:56 +04: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-21 21:03:40 +04:00
</varlistentry>
2010-07-07 03:38:56 +04:00
</variablelist>
</refsect1>
<refsect1 >
<title > See Also</title>
<para >
2013-01-15 07:08:33 +04:00
<citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.directives</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry>
2010-07-07 03:38:56 +04:00
</para>
</refsect1>
</refentry>
