1 <?xml version='1.0'?> <!--*-nxml-*-->
2 <?xml-stylesheet type="text/xsl" href="http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl"?>
3 <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
4 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
7 This file is part of systemd.
9 Copyright 2010 Lennart Poettering
11 systemd is free software; you can redistribute it and/or modify it
12 under the terms of the GNU Lesser General Public License as published by
13 the Free Software Foundation; either version 2.1 of the License, or
14 (at your option) any later version.
16 systemd is distributed in the hope that it will be useful, but
17 WITHOUT ANY WARRANTY; without even the implied warranty of
18 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
19 Lesser General Public License for more details.
21 You should have received a copy of the GNU Lesser General Public License
22 along with systemd; If not, see <http://www.gnu.org/licenses/>.
25 <refentry id="systemd.conf">
27 <title>systemd.conf</title>
28 <productname>systemd</productname>
32 <contrib>Developer</contrib>
33 <firstname>Lennart</firstname>
34 <surname>Poettering</surname>
35 <email>lennart@poettering.net</email>
41 <refentrytitle>systemd.conf</refentrytitle>
42 <manvolnum>5</manvolnum>
46 <refname>systemd.conf</refname>
47 <refpurpose>systemd manager configuration file</refpurpose>
51 <para><filename>system.conf</filename></para>
52 <para><filename>user.conf</filename></para>
56 <title>Description</title>
58 <para>When run as system instance systemd reads the
59 configuration file <filename>system.conf</filename>,
60 otherwise <filename>user.conf</filename>. These
61 configuration files contain a few settings controlling
62 basic manager operations.</para>
67 <title>Options</title>
69 <para>All options are configured in the
70 <literal>[Manager]</literal> section:</para>
75 <term><varname>LogLevel=</varname></term>
76 <term><varname>LogTarget=</varname></term>
77 <term><varname>LogColor=</varname></term>
78 <term><varname>LogLocation=</varname></term>
79 <term><varname>DumpCore=yes</varname></term>
80 <term><varname>CrashShell=no</varname></term>
81 <term><varname>ShowStatus=yes</varname></term>
82 <term><varname>SysVConsole=yes</varname></term>
83 <term><varname>CrashChVT=1</varname></term>
84 <term><varname>DefaultStandardOutput=journal</varname></term>
85 <term><varname>DefaultStandardError=inherit</varname></term>
87 <listitem><para>Configures various
88 parameters of basic manager
89 operation. These options may be
90 overridden by the respective command
92 <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>
93 for details about these command line
94 arguments.</para></listitem>
98 <term><varname>CPUAffinity=</varname></term>
100 <listitem><para>Configures the initial
101 CPU affinity for the init
102 process. Takes a space-separated list
103 of CPU indexes.</para></listitem>
107 <term><varname>DefaultControllers=cpu</varname></term>
109 <listitem><para>Configures in which
110 cgroup controller hierarchies to
111 create per-service cgroups
112 automatically, in addition to the
113 name=systemd named hierarchy. Defaults
114 to 'cpu'. Takes a space separated list
115 of controller names. Pass an empty
116 string to ensure that systemd does not
117 touch any hierarchies but its
118 own.</para></listitem>
122 <term><varname>JoinControllers=cpu,cpuacct</varname></term>
124 <listitem><para>Configures controllers
125 that shall be mounted in a single
126 hierarchy. By default systemd will
127 mount all controllers which are
128 enabled in the kernel in individual
129 hierachies, with the exception of
130 those listed in this setting. Takes a
131 space separated list of comma
132 separated controller names, in order
133 to allow multiple joined
134 hierarchies. Defaults to
135 'cpu,cpuacct'. Pass an empty string to
136 ensure that systemd mounts all
137 controllers in separate
138 hierarchies.</para></listitem>
142 <term><varname>RuntimeWatchdogSec=</varname></term>
143 <term><varname>ShutdownWatchdogSec=</varname></term>
145 <listitem><para>Configure the hardware
146 watchdog at runtime and at
147 reboot. Takes a timeout value in
148 seconds (or in other time units if
149 suffixed with <literal>ms</literal>,
150 <literal>min</literal>,
151 <literal>h</literal>,
152 <literal>d</literal>,
153 <literal>w</literal>). If
154 <varname>RuntimeWatchdogSec=</varname>
155 is set to a non-zero value the
157 (<filename>/dev/watchdog</filename>)
158 will be programmed to automatically
159 reboot the system if it is not
160 contacted within the specified timeout
161 interval. The system manager will
162 ensure to contact it at least once in
163 half the specified timeout
164 interval. This feature requires a
165 hardware watchdog device to be
166 present, as it is commonly the case in
167 embedded and server systems. Not all
168 hardware watchdogs allow configuration
169 of the reboot timeout, in which case
170 the closest available timeout is
171 picked. <varname>ShutdownWatchdogSec=</varname>
172 may be used to configure the hardware
173 watchdog when the system is asked to
174 reboot. It works as a safety net to
175 ensure that the reboot takes place
176 even if a clean reboot attempt times
178 <varname>RuntimeWatchdogSec=</varname>
179 defaults to 0 (off), and
180 <varname>ShutdownWatchdogSec=</varname>
181 to 10min. These settings have no
182 effect if a hardware watchdog is not
183 available.</para></listitem>
187 <term><varname>CapabilityBoundingSet=</varname></term>
189 <listitem><para>Controls which
190 capabilities to include in the
191 capability bounding set for PID 1 and
193 <citerefentry><refentrytitle>capabilities</refentrytitle><manvolnum>7</manvolnum></citerefentry>
194 for details. Takes a whitespace
195 separated list of capability names as
197 <citerefentry><refentrytitle>cap_from_name</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
198 Capabilities listed will be included
199 in the bounding set, all others are
200 removed. If the list of capabilities
201 is prefixed with ~ all but the listed
202 capabilities will be included, the
203 effect of the assignment
204 inverted. Note that this option also
205 effects the respective capabilities in
206 the effective, permitted and
207 inheritable capability sets. The
208 capability bounding set may also be
209 individually configured for units
211 <varname>CapabilityBoundingSet=</varname>
212 directive for units, but note that
213 capabilities dropped for PID 1 cannot
214 be regained in individual units, they
215 are lost for good.</para></listitem>
219 <term><varname>TimerSlackNSec=</varname></term>
221 <listitem><para>Sets the timer slack
222 in nanoseconds for PID 1 which is then
223 inherited to all executed processes,
224 unless overriden individually, for
226 <varname>TimerSlackNSec=</varname>
227 setting in service units (for details
229 <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>). The
230 timer slack controls the accuracy of
231 wake-ups triggered by timers. See
232 <citerefentry><refentrytitle>prctl</refentrytitle><manvolnum>2</manvolnum></citerefentry>
233 for more information. Note that in
234 contrast to most other time span
235 definitions this parameter takes an
236 integer value in nano-seconds if no
237 unit is specified. The usual time
239 too.</para></listitem>
243 <term><varname>DefaultLimitCPU=</varname></term>
244 <term><varname>DefaultLimitFSIZE=</varname></term>
245 <term><varname>DefaultLimitDATA=</varname></term>
246 <term><varname>DefaultLimitSTACK=</varname></term>
247 <term><varname>DefaultLimitCORE=</varname></term>
248 <term><varname>DefaultLimitRSS=</varname></term>
249 <term><varname>DefaultLimitNOFILE=</varname></term>
250 <term><varname>DefaultLimitAS=</varname></term>
251 <term><varname>DefaultLimitNPROC=</varname></term>
252 <term><varname>DefaultLimitMEMLOCK=</varname></term>
253 <term><varname>DefaultLimitLOCKS=</varname></term>
254 <term><varname>DefaultLimitSIGPENDING=</varname></term>
255 <term><varname>DefaultLimitMSGQUEUE=</varname></term>
256 <term><varname>DefaultLimitNICE=</varname></term>
257 <term><varname>DefaultLimitRTPRIO=</varname></term>
258 <term><varname>DefaultLimitRTTIME=</varname></term>
260 <listitem><para>These settings control
261 various default resource limits for
263 <citerefentry><refentrytitle>setrlimit</refentrytitle><manvolnum>2</manvolnum></citerefentry>
264 for details. Use the string
265 <varname>infinity</varname> to
266 configure no limit on a specific
267 resource. These settings may be
268 overriden in individual units
269 using the corresponding LimitXXX=
270 directives. Note that these resource
271 limits are only defaults for units,
272 they are not applied to PID 1
273 itself.</para></listitem>
279 <title>See Also</title>
281 <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>