Debian Codegraph @

upstream/debian-unstable/man5/systemd-system.conf.5

raw
1 '\" t
2 .TH "SYSTEMD\-SYSTEM\&.CONF" "5" "" "systemd 261~rc3" "systemd-system.conf"
3 .\" -----------------------------------------------------------------
4 .\" * Define some portability stuff
5 .\" -----------------------------------------------------------------
6 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
7 .\" http://bugs.debian.org/507673
8 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
9 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
10 .ie \n(.g .ds Aq \(aq
11 .el .ds Aq '
12 .\" -----------------------------------------------------------------
13 .\" * set default formatting
14 .\" -----------------------------------------------------------------
15 .\" disable hyphenation
16 .nh
17 .\" disable justification (adjust text to left margin only)
18 .ad l
19 .\" -----------------------------------------------------------------
20 .\" * MAIN CONTENT STARTS HERE *
21 .\" -----------------------------------------------------------------
22 .SH "NAME"
23 systemd-system.conf, system.conf.d, systemd-user.conf, user.conf.d \- System and session service manager configuration files
24 .SH "SYNOPSIS"
25 .PP
26 /etc/systemd/system\&.conf,
27 /run/systemd/system\&.conf,
28 /usr/lib/systemd/system\&.conf,
29 /etc/systemd/system\&.conf\&.d/*\&.conf,
30 /run/systemd/system\&.conf\&.d/*\&.conf,
31 /usr/lib/systemd/system\&.conf\&.d/*\&.conf
32 .PP
33 ~/\&.config/systemd/user\&.conf,
34 /etc/systemd/user\&.conf,
35 /run/systemd/user\&.conf,
36 /usr/lib/systemd/user\&.conf,
37 /etc/systemd/user\&.conf\&.d/*\&.conf,
38 /run/systemd/user\&.conf\&.d/*\&.conf,
39 /usr/lib/systemd/user\&.conf\&.d/*\&.conf
40 .SH "DESCRIPTION"
41 .PP
42 When run as a system instance,
43 \fBsystemd\fR
44 interprets the configuration file
45 system\&.conf
46 and the files in
47 system\&.conf\&.d
48 directories; when run as a user instance, it interprets the configuration file
49 user\&.conf
50 (in order of priority, in the home directory of the user and under
51 /etc/systemd/,
52 /run/systemd/, and
53 /usr/lib/systemd/) and the files in
54 user\&.conf\&.d
55 directories\&. These configuration files contain a few settings controlling basic manager operations\&.
56 .PP
57 See
58 \fBsystemd.syntax\fR(7)
59 for a general description of the syntax\&.
60 .SH "CONFIGURATION DIRECTORIES AND PRECEDENCE"
61 .PP
62 The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is loaded from one of the listed directories in order of priority, only the first file found is used:
63 /etc/systemd/,
64 /run/systemd/,
65 /usr/local/lib/systemd/
66 \&\s-2\u[1]\d\s+2,
67 /usr/lib/systemd/\&. The vendor version of the file contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can also be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
68 /etc/
69 if it is shipped under
70 /usr/), however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
71 .PP
72 In addition to the main configuration file, drop\-in configuration snippets are read from
73 /usr/lib/systemd/*\&.conf\&.d/,
74 /usr/local/lib/systemd/*\&.conf\&.d/, and
75 /etc/systemd/*\&.conf\&.d/\&. Those drop\-ins have higher precedence and override the main configuration file\&. Files in the
76 *\&.conf\&.d/
77 configuration subdirectories are sorted by their filename in lexicographic order, regardless of in which of the subdirectories they reside\&. When multiple files specify the same option, for options which accept just a single value, the entry in the file sorted last takes precedence, and for options which accept a list of values, entries are collected as they occur in the sorted files\&.
78 .PP
79 When packages need to customize the configuration, they can install drop\-ins under
80 /usr/\&. Files in
81 /etc/
82 are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering\&. This also defines a concept of drop\-in priorities to allow OS vendors to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&. It is recommended to use the range 10\-40 for drop\-ins in
83 /usr/
84 and the range 60\-90 for drop\-ins in
85 /etc/
86 and
87 /run/, to make sure that local and transient drop\-ins take priority over drop\-ins shipped by the OS vendor\&.
88 .PP
89 To disable a configuration file supplied by the vendor, the recommended way is to place a symlink to
90 /dev/null
91 in the configuration directory in
92 /etc/, with the same filename as the vendor configuration file\&.
93 .SH "OPTIONS"
94 .PP
95 All options are configured in the [Manager] section:
96 .PP
97 \fILogColor=\fR, \fILogLevel=\fR, \fILogLocation=\fR, \fILogTarget=\fR, \fILogTime=\fR, \fIDumpCore=yes\fR, \fICrashChangeVT=no\fR, \fICrashShell=no\fR, \fICrashAction=freeze\fR, \fIShowStatus=yes\fR, \fIDefaultStandardOutput=journal\fR, \fIDefaultStandardError=inherit\fR
98 .RS 4
99 Configures various parameters of basic manager operation\&. These options may be overridden by the respective process and kernel command line arguments\&. See
100 \fBsystemd\fR(1)
101 for details\&.
102 .sp
103 Added in version 198\&.
104 .RE
105 .PP
106 \fICtrlAltDelBurstAction=\fR
107 .RS 4
108 Defines what action will be performed if user presses Ctrl\-Alt\-Delete more than 7 times in 2s\&. Can be set to
109 "reboot\-force",
110 "poweroff\-force",
111 "reboot\-immediate",
112 "poweroff\-immediate"
113 or disabled with
114 "none"\&. Defaults to
115 "reboot\-force"\&.
116 .sp
117 Added in version 232\&.
118 .RE
119 .PP
120 \fIStatusUnitFormat=\fR
121 .RS 4
122 Takes
123 \fBname\fR,
124 \fBdescription\fR
125 or
126 \fBcombined\fR
127 as the value\&. If
128 \fBname\fR, the system manager will use unit names in status messages (e\&.g\&.
129 "systemd\-journald\&.service"), instead of the longer and more informative descriptions set with
130 \fIDescription=\fR
131 (e\&.g\&.
132 "Journal Logging Service")\&. If
133 \fBcombined\fR, the system manager will use both unit names and descriptions in status messages (e\&.g\&.
134 "systemd\-journald\&.service \- Journal Logging Service")\&.
135 .sp
136 See
137 \fBsystemd.unit\fR(5)
138 for details about unit names and
139 \fIDescription=\fR\&.
140 .sp
141 Added in version 243\&.
142 .RE
143 .PP
144 \fIDefaultTimerAccuracySec=\fR
145 .RS 4
146 Sets the default accuracy of timer units\&. This controls the global default for the
147 \fIAccuracySec=\fR
148 setting of timer units, see
149 \fBsystemd.timer\fR(5)
150 for details\&.
151 \fIAccuracySec=\fR
152 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
153 \fITimerSlackNSec=\fR
154 above\&.
155 .sp
156 Added in version 212\&.
157 .RE
158 .SH "RESOURCE MANAGEMENT"
159 .PP
160 \fITimerSlackNSec=\fR
161 .RS 4
162 Sets the timer slack in nanoseconds for PID 1, which is inherited by all executed processes, unless overridden individually, for example with the
163 \fITimerSlackNSec=\fR
164 setting in service units (for details see
165 \fBsystemd.exec\fR(5))\&. The timer slack controls the accuracy of wake\-ups triggered by system timers\&. See
166 \fBprctl\fR(2)
167 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\&.
168 .sp
169 Added in version 198\&.
170 .RE
171 .PP
172 \fICPUAffinity=\fR
173 .RS 4
174 Configures the CPU affinity for the service manager as well as the default CPU affinity for all forked off processes\&. Takes a list of CPU indices or ranges separated by either whitespace or commas\&. CPU ranges are specified by the lower and upper CPU indices separated by a dash\&. This option may be specified more than once, in which case the specified CPU affinity masks are merged\&. If the empty string is assigned, the mask is reset, all assignments prior to this will have no effect\&. Individual services may override the CPU affinity for their processes with the
175 \fICPUAffinity=\fR
176 setting in unit files, see
177 \fBsystemd.exec\fR(5)\&.
178 .sp
179 Added in version 198\&.
180 .RE
181 .PP
182 \fINUMAPolicy=\fR
183 .RS 4
184 Configures the NUMA memory policy for the service manager and the default NUMA memory policy for all forked off processes\&. Individual services may override the default policy with the
185 \fINUMAPolicy=\fR
186 setting in unit files, see
187 \fBsystemd.exec\fR(5)\&.
188 .sp
189 Added in version 243\&.
190 .RE
191 .PP
192 \fINUMAMask=\fR
193 .RS 4
194 Configures the NUMA node mask that will be associated with the selected NUMA policy\&. Note that
195 \fBdefault\fR
196 and
197 \fBlocal\fR
198 NUMA policies do not require explicit NUMA node mask and value of the option can be empty\&. Similarly to
199 \fINUMAPolicy=\fR, value can be overridden by individual services in unit files, see
200 \fBsystemd.exec\fR(5)\&.
201 .sp
202 Added in version 243\&.
203 .RE
204 .PP
205 \fIDefaultMemoryAccounting=\fR, \fIDefaultTasksAccounting=\fR, \fIDefaultIOAccounting=\fR, \fIDefaultIPAccounting=\fR
206 .RS 4
207 Configure the default resource accounting settings, as configured per\-unit by
208 \fIMemoryAccounting=\fR,
209 \fITasksAccounting=\fR,
210 \fIIOAccounting=\fR, and
211 \fIIPAccounting=\fR\&. See
212 \fBsystemd.resource-control\fR(5)
213 for details on the per\-unit settings\&.
214 .sp
215 \fIDefaultMemoryAccounting=\fR
216 defaults to yes\&.
217 \fIDefaultTasksAccounting=\fR
218 defaults to yes\&. The other settings default to no\&.
219 .sp
220 Added in version 211\&.
221 .RE
222 .PP
223 \fIDefaultTasksMax=\fR
224 .RS 4
225 Configure the default value for the per\-unit
226 \fITasksMax=\fR
227 setting\&. See
228 \fBsystemd.resource-control\fR(5)
229 for details\&. This setting applies to all unit types that support resource control settings, with the exception of slice units\&. Defaults to 15% of the minimum of
230 \fIkernel\&.pid_max=\fR,
231 \fIkernel\&.threads\-max=\fR
232 and root cgroup
233 \fIpids\&.max\fR\&. Kernel has a default value for
234 \fIkernel\&.pid_max=\fR
235 and an algorithm of counting in case of more than 32 cores\&. For example, with the default
236 \fIkernel\&.pid_max=\fR,
237 \fIDefaultTasksMax=\fR
238 defaults to 4915, but might be greater in other systems or smaller in OS containers\&.
239 .sp
240 Added in version 228\&.
241 .RE
242 .PP
243 \fIDefaultLimitCPU=\fR, \fIDefaultLimitFSIZE=\fR, \fIDefaultLimitDATA=\fR, \fIDefaultLimitSTACK=\fR, \fIDefaultLimitCORE=\fR, \fIDefaultLimitRSS=\fR, \fIDefaultLimitNOFILE=\fR, \fIDefaultLimitAS=\fR, \fIDefaultLimitNPROC=\fR, \fIDefaultLimitMEMLOCK=\fR, \fIDefaultLimitLOCKS=\fR, \fIDefaultLimitSIGPENDING=\fR, \fIDefaultLimitMSGQUEUE=\fR, \fIDefaultLimitNICE=\fR, \fIDefaultLimitRTPRIO=\fR, \fIDefaultLimitRTTIME=\fR
244 .RS 4
245 These settings control various default resource limits for processes executed by units\&. See
246 \fBsetrlimit\fR(2)
247 for details\&. These settings may be overridden in individual units using the corresponding
248 \fILimitXXX=\fR
249 directives and they accept the same parameter syntax, see
250 \fBsystemd.exec\fR(5)
251 for details\&. Note that these resource limits are only defaults for units, they are not applied to the service manager process (i\&.e\&. PID 1) itself\&.
252 .sp
253 Most of these settings are unset, which means the resource limits are inherited from the kernel or, if invoked in a container, from the container manager\&. However, the following have defaults:
254 .sp
255 .RS 4
256 .ie n \{\
257 \h'-04'\(bu\h'+03'\c
258 .\}
259 .el \{\
260 .sp -1
261 .IP \(bu 2.3
262 .\}
263 \fIDefaultLimitNOFILE=\fR
264 defaults to 1024:524288\&.
265 .RE
266 .sp
267 .RS 4
268 .ie n \{\
269 \h'-04'\(bu\h'+03'\c
270 .\}
271 .el \{\
272 .sp -1
273 .IP \(bu 2.3
274 .\}
275 \fIDefaultLimitMEMLOCK=\fR
276 defaults to 8M\&.
277 .RE
278 .sp
279 .RS 4
280 .ie n \{\
281 \h'-04'\(bu\h'+03'\c
282 .\}
283 .el \{\
284 .sp -1
285 .IP \(bu 2.3
286 .\}
287 \fIDefaultLimitCORE=\fR
288 does not have a default but it is worth mentioning that
289 \fIRLIMIT_CORE\fR
290 is set to
291 "infinity"
292 by PID 1 which is inherited by its children\&.
293 .RE
294 .sp
295 Note that the service manager internally in PID 1 bumps
296 \fIRLIMIT_NOFILE\fR
297 and
298 \fIRLIMIT_MEMLOCK\fR
299 to higher values, however the limit is reverted to the mentioned defaults for all child processes forked off\&.
300 .sp
301 Added in version 198\&.
302 .RE
303 .PP
304 \fIDefaultOOMPolicy=\fR
305 .RS 4
306 Configure the default policy for reacting to processes being killed by the Linux Out\-Of\-Memory (OOM) killer or
307 \fBsystemd\-oomd\fR\&. This may be used to pick a global default for the per\-unit
308 \fIOOMPolicy=\fR
309 setting\&. See
310 \fBsystemd.service\fR(5)
311 for details\&. Note that this default is not used for services that have
312 \fIDelegate=\fR
313 turned on\&.
314 .sp
315 Added in version 243\&.
316 .RE
317 .PP
318 \fIDefaultOOMScoreAdjust=\fR
319 .RS 4
320 Configures the default OOM score adjustments of processes run by the service manager\&. This defaults to unset (meaning the forked off processes inherit the service manager\*(Aqs OOM score adjustment value), except if the service manager is run for an unprivileged user, in which case this defaults to the service manager\*(Aqs OOM adjustment value plus 100 (this makes service processes slightly more likely to be killed under memory pressure than the manager itself)\&. This may be used to pick a global default for the per\-unit
321 \fIOOMScoreAdjust=\fR
322 setting\&. See
323 \fBsystemd.exec\fR(5)
324 for details\&. Note that this setting has no effect on the OOM score adjustment value of the service manager process itself, it retains the original value set during its invocation\&.
325 .sp
326 Added in version 250\&.
327 .RE
328 .PP
329 \fIDefaultMemoryPressureWatch=\fR, \fIDefaultMemoryPressureThresholdSec=\fR
330 .RS 4
331 Configures the default settings for the per\-unit
332 \fIMemoryPressureWatch=\fR
333 and
334 \fIMemoryPressureThresholdSec=\fR
335 settings\&. See
336 \fBsystemd.resource-control\fR(5)
337 for details\&. Defaults to
338 "auto"
339 and
340 "200ms", respectively\&. This also sets the memory pressure monitoring threshold for the service manager itself\&.
341 .sp
342 Added in version 254\&.
343 .RE
344 .PP
345 \fIDefaultCPUPressureWatch=\fR, \fIDefaultCPUPressureThresholdSec=\fR
346 .RS 4
347 Configures the default settings for the per\-unit
348 \fICPUPressureWatch=\fR
349 and
350 \fICPUPressureThresholdSec=\fR
351 settings\&. See
352 \fBsystemd.resource-control\fR(5)
353 for details\&. Defaults to
354 "auto"
355 and
356 "200ms", respectively\&. This also sets the CPU pressure monitoring threshold for the service manager itself\&.
357 .sp
358 Added in version 261\&.
359 .RE
360 .PP
361 \fIDefaultIOPressureWatch=\fR, \fIDefaultIOPressureThresholdSec=\fR
362 .RS 4
363 Configures the default settings for the per\-unit
364 \fIIOPressureWatch=\fR
365 and
366 \fIIOPressureThresholdSec=\fR
367 settings\&. See
368 \fBsystemd.resource-control\fR(5)
369 for details\&. Defaults to
370 "auto"
371 and
372 "200ms", respectively\&. This also sets the IO pressure monitoring threshold for the service manager itself\&.
373 .sp
374 Added in version 261\&.
375 .RE
376 .SH "HARDWARE WATCHDOG"
377 .PP
378 \fIRuntimeWatchdogSec=\fR, \fIRebootWatchdogSec=\fR, \fIKExecWatchdogSec=\fR
379 .RS 4
380 Configure the hardware watchdog at runtime and at reboot\&. Takes a timeout value in seconds (or in other time units if suffixed with
381 "ms",
382 "min",
383 "h",
384 "d",
385 "w"), or the special strings
386 "off"
387 or
388 "default"\&. If set to
389 "off"
390 (alternatively:
391 "0") the watchdog logic is disabled: no watchdog device is opened, configured, or pinged\&. If set to the special string
392 "default"
393 the watchdog is opened and pinged in regular intervals, but the timeout is not changed from the default\&. If set to any other time value the watchdog timeout is configured to the specified value (or a value close to it, depending on hardware capabilities)\&.
394 .sp
395 If
396 \fIRuntimeWatchdogSec=\fR
397 is set to a non\-zero value, the watchdog hardware (/dev/watchdog0
398 or the path specified with
399 \fIWatchdogDevice=\fR
400 or the kernel option
401 \fIsystemd\&.watchdog_device=\fR) 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 all possible reboot timeout values, in which case the closest available timeout is picked\&.
402 .sp
403 \fIRebootWatchdogSec=\fR
404 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\&. Note that the
405 \fIRebootWatchdogSec=\fR
406 timeout applies only to the second phase of the reboot, i\&.e\&. after all regular services are already terminated, and after the system and service manager process (PID 1) got replaced by the
407 systemd\-shutdown
408 binary, see system
409 \fBbootup\fR(7)
410 for details\&. During the first phase of the shutdown operation the system and service manager remains running and hence
411 \fIRuntimeWatchdogSec=\fR
412 is still honoured\&. In order to define a timeout on this first phase of system shutdown, configure
413 \fIJobTimeoutSec=\fR
414 and
415 \fIJobTimeoutAction=\fR
416 in the [Unit] section of the
417 shutdown\&.target
418 unit\&. By default,
419 \fIRuntimeWatchdogSec=\fR
420 defaults to 0 (off), and
421 \fIRebootWatchdogSec=\fR
422 to 10min\&.
423 .sp
424 \fIKExecWatchdogSec=\fR
425 may be used to additionally enable the watchdog when kexec is being executed rather than when rebooting\&. Note that if the kernel does not reset the watchdog on kexec (depending on the specific hardware and/or driver), in this case the watchdog might not get disabled after kexec succeeds and thus the system might get rebooted, unless
426 \fIRuntimeWatchdogSec=\fR
427 is also enabled at the same time\&. For this reason it is recommended to enable
428 \fIKExecWatchdogSec=\fR
429 only if
430 \fIRuntimeWatchdogSec=\fR
431 is also enabled\&.
432 .sp
433 These settings have no effect if a hardware watchdog is not available\&.
434 .sp
435 Added in version 198\&.
436 .RE
437 .PP
438 \fIRuntimeWatchdogPreSec=\fR
439 .RS 4
440 Configure the hardware watchdog device pre\-timeout value\&. Takes a timeout value in seconds (or in other time units similar to
441 \fIRuntimeWatchdogSec=\fR)\&. A watchdog pre\-timeout is a notification generated by the watchdog before the watchdog reset might occur in the event the watchdog has not been serviced\&. This notification is handled by the kernel and can be configured to take an action (i\&.e\&. generate a kernel panic) using
442 \fIRuntimeWatchdogPreGovernor=\fR\&. Not all watchdog hardware or drivers support generating a pre\-timeout and depending on the state of the system, the kernel may be unable to take the configured action before the watchdog reboot\&. The watchdog will be configured to generate the pre\-timeout event at the amount of time specified by
443 \fIRuntimeWatchdogPreSec=\fR
444 before the runtime watchdog timeout (set by
445 \fIRuntimeWatchdogSec=\fR)\&. For example, if the we have
446 \fIRuntimeWatchdogSec=30\fR
447 and
448 \fIRuntimeWatchdogPreSec=10\fR, then the pre\-timeout event will occur if the watchdog has not pinged for 20s (10s before the watchdog would fire)\&. By default,
449 \fIRuntimeWatchdogPreSec=\fR
450 defaults to 0 (off)\&. The value set for
451 \fIRuntimeWatchdogPreSec=\fR
452 must be smaller than the timeout value for
453 \fIRuntimeWatchdogSec=\fR\&. This setting has no effect if a hardware watchdog is not available or the hardware watchdog does not support a pre\-timeout and will be ignored by the kernel if the setting is greater than the actual watchdog timeout\&.
454 .sp
455 Added in version 251\&.
456 .RE
457 .PP
458 \fIRuntimeWatchdogPreGovernor=\fR
459 .RS 4
460 Configure the action taken by the hardware watchdog device when the pre\-timeout expires\&. The default action for the pre\-timeout event depends on the kernel configuration, but it is usually to log a kernel message\&. For a list of valid actions available for a given watchdog device, check the content of the
461 /sys/class/watchdog/watchdog\fIX\fR/pretimeout_available_governors
462 file\&. Typically, available governor types are
463 \fInoop\fR
464 and
465 \fIpanic\fR\&. Availability, names and functionality might vary depending on the specific device driver in use\&. If the
466 pretimeout_available_governors
467 sysfs file is empty, the governor might be built as a kernel module and might need to be manually loaded (e\&.g\&.
468 \fIpretimeout_noop\&.ko\fR), or the watchdog device might not support pre\-timeouts\&.
469 .sp
470 Added in version 251\&.
471 .RE
472 .PP
473 \fIWatchdogDevice=\fR
474 .RS 4
475 Configure the hardware watchdog device that the runtime and shutdown watchdog timers will open and use\&. Defaults to
476 /dev/watchdog0\&. This setting has no effect if a hardware watchdog is not available\&.
477 .sp
478 Added in version 236\&.
479 .RE
480 .SH "SECURITY"
481 .PP
482 \fICapabilityBoundingSet=\fR
483 .RS 4
484 Controls which capabilities to include in the capability bounding set for PID 1 and its children\&. See
485 \fBcapabilities\fR(7)
486 for details\&. Takes a whitespace\-separated list of capability names as read by
487 \fBcap_from_name\fR(3)\&. 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 affects the respective capabilities in the effective, permitted and inheritable capability sets\&. The capability bounding set may also be individually configured for units using the
488 \fICapabilityBoundingSet=\fR
489 directive for units, but note that capabilities dropped for PID 1 cannot be regained in individual units, they are lost for good\&.
490 .sp
491 Added in version 198\&.
492 .RE
493 .PP
494 \fINoNewPrivileges=\fR
495 .RS 4
496 Takes a boolean argument\&. If true, ensures that PID 1 and all its children can never gain new privileges through
497 \fBexecve\fR(2)
498 (e\&.g\&. via setuid or setgid bits, or filesystem capabilities)\&. Defaults to false\&. General purpose distributions commonly rely on executables with setuid or setgid bits and will thus not function properly with this option enabled\&. Individual units cannot disable this option\&. Also see
499 \m[blue]\fBNo New Privileges Flag\fR\m[]\&\s-2\u[2]\d\s+2\&.
500 .sp
501 Added in version 239\&.
502 .RE
503 .PP
504 \fIProtectSystem=\fR
505 .RS 4
506 Takes a boolean argument or the string
507 "auto"\&. If set to true this will remount
508 /usr/
509 read\-only\&. If set to
510 "auto"
511 (the default) and running in an initrd equivalent to true, otherwise false\&. This implements a restricted subset of the per\-unit setting of the same name, see
512 \fBsystemd.exec\fR(5)
513 for details: currently, the
514 "full"
515 or
516 "strict"
517 values are not supported\&.
518 .sp
519 Added in version 256\&.
520 .RE
521 .PP
522 \fIRestrictFileSystemAccess=\fR
523 .RS 4
524 Takes a boolean argument or the special value
525 "exec"\&. Defaults to
526 "no"\&. When enabled, PID 1 loads a BPF LSM program that enforces a deny\-default execution policy: only binaries residing on signed dm\-verity block devices (and the initramfs during early boot) are permitted to execute\&. Execution from tmpfs, procfs, sysfs, unsigned dm\-verity devices, and anonymous executable memory mappings is denied\&.
527 .sp
528 This setting is intended as one component of an image\-based, fully verified system, where the whole boot chain (firmware, kernel image, kernel command line, initramfs) is measured and attested\&. On a general\-purpose system without such guarantees it does not provide a meaningful security boundary on its own: an attacker with sufficient privilege to edit
529 system\&.conf, modify the kernel command line, or kexec into an unsigned initrd can disable or bypass the policy\&.
530 .sp
531 The enforcement hooks block
532 \fBexecve()\fR
533 of untrusted binaries ("bprm_check_security"),
534 \fBPROT_EXEC\fR
535 memory mappings including shared libraries ("mmap_file"), and write\-to\-execute transitions such as JIT compilation ("file_mprotect")\&.
536 .sp
537 Note that execution from overlayfs mounts is blocked even if the underlying layers reside on signed dm\-verity devices, because the BPF program sees the overlay filesystem\*(Aqs anonymous device number rather than the underlying block device\&. Multi\-device filesystems such as btrfs are similarly unsupported\&.
538 .sp
539 Note that, without further measures to secure the system, kexec can be used to circumvent this\&.
540 .sp
541 This requires the kernel to be booted with
542 "dm_verity\&.require_signatures=1"
543 on the kernel command line and with BPF LSM enabled ("lsm=\&.\&.\&.,bpf")\&. If either prerequisite is not met, PID 1 will refuse to complete startup\&.
544 .sp
545 The value
546 "yes"
547 is equivalent to
548 "exec"\&. Additional modes may be added in the future\&.
549 .sp
550 This option may also be set via the
551 \fIsystemd\&.restrict_filesystem_access=\fR
552 kernel command line option, see
553 \fBkernel-command-line\fR(7)\&.
554 .sp
555 Added in version 261\&.
556 .RE
557 .PP
558 \fISystemCallArchitectures=\fR
559 .RS 4
560 Takes a space\-separated list of architecture identifiers\&. Selects from which 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 execution of 32\-bit x86 binaries on 64\-bit x86\-64 systems\&. This option operates system\-wide, and acts similar to the
561 \fISystemCallArchitectures=\fR
562 setting of unit files, see
563 \fBsystemd.exec\fR(5)
564 for details\&. This setting defaults to the empty list, in which case no filtering of system calls based on architecture is applied\&. Known architecture identifiers are
565 "x86",
566 "x86\-64",
567 "x32",
568 "arm"
569 and the special identifier
570 "native"\&. 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
571 "native"
572 to prohibit execution of any non\-native binaries\&. When a binary executes a system call of an architecture that is not listed in this setting, it will be immediately terminated with the SIGSYS signal\&.
573 .sp
574 Added in version 209\&.
575 .RE
576 .PP
577 \fIDefaultSmackProcessLabel=\fR
578 .RS 4
579 Takes a
580 \fBSMACK64\fR
581 security label as the argument\&. The process executed by a unit will be started under this label if
582 \fISmackProcessLabel=\fR
583 is not set in the unit\&. See
584 \fBsystemd.exec\fR(5)
585 for the details\&.
586 .sp
587 If the value is
588 "/", only labels specified with
589 \fISmackProcessLabel=\fR
590 are assigned and the compile\-time default is ignored\&.
591 .sp
592 Added in version 252\&.
593 .RE
594 .PP
595 \fIDefaultRestrictSUIDSGID=\fR
596 .RS 4
597 Takes a boolean argument\&. This is used as a default for units which lack an explicit definition for
598 \fIRestrictSUIDSGID=\fR\&. See
599 \fBsystemd.exec\fR(5)
600 for the details\&.
601 .sp
602 Added in version 258\&.
603 .RE
604 .SH "TIMEOUTS AND RATE LIMITS"
605 .PP
606 \fIDefaultTimeoutStartSec=\fR, \fIDefaultTimeoutStopSec=\fR, \fIDefaultTimeoutAbortSec=\fR, \fIDefaultRestartSec=\fR
607 .RS 4
608 Configures the default timeouts for starting, stopping and aborting of units, as well as the default time to sleep between automatic restarts of units, as configured per\-unit in
609 \fITimeoutStartSec=\fR,
610 \fITimeoutStopSec=\fR,
611 \fITimeoutAbortSec=\fR
612 and
613 \fIRestartSec=\fR
614 (for services, see
615 \fBsystemd.service\fR(5)
616 for details on the per\-unit settings)\&. For non\-service units,
617 \fIDefaultTimeoutStartSec=\fR
618 sets the default
619 \fITimeoutSec=\fR
620 value\&.
621 .sp
622 \fIDefaultTimeoutStartSec=\fR
623 and
624 \fIDefaultTimeoutStopSec=\fR
625 default to 90 s in the system manager and 90 s in the user manager\&.
626 \fIDefaultTimeoutAbortSec=\fR
627 is not set by default so that all units fall back to
628 \fITimeoutStopSec=\fR\&.
629 \fIDefaultRestartSec=\fR
630 defaults to 100 ms\&.
631 .sp
632 Added in version 209\&.
633 .RE
634 .PP
635 \fIDefaultDeviceTimeoutSec=\fR
636 .RS 4
637 Configures the default timeout for waiting for devices\&. It can be changed per device via the
638 \fIx\-systemd\&.device\-timeout=\fR
639 option in
640 /etc/fstab
641 and
642 /etc/crypttab
643 (see
644 \fBsystemd.mount\fR(5),
645 \fBcrypttab\fR(5))\&. Defaults to 90 s in the system manager and 90 s in the user manager\&.
646 .sp
647 Added in version 252\&.
648 .RE
649 .PP
650 \fIDefaultStartLimitIntervalSec=\fR, \fIDefaultStartLimitBurst=\fR
651 .RS 4
652 Configure the default unit start rate limiting, as configured per\-service by
653 \fIStartLimitIntervalSec=\fR
654 and
655 \fIStartLimitBurst=\fR\&. See
656 \fBsystemd.service\fR(5)
657 for details on the per\-service settings\&.
658 \fIDefaultStartLimitIntervalSec=\fR
659 defaults to 10s\&.
660 \fIDefaultStartLimitBurst=\fR
661 defaults to 5\&.
662 .sp
663 Added in version 209\&.
664 .RE
665 .PP
666 \fIReloadLimitIntervalSec=\fR, \fIReloadLimitBurst=\fR
667 .RS 4
668 Rate limiting for daemon\-reload and (since v256) daemon\-reexec requests\&. The setting applies to both operations, but the rate limits are tracked separately\&. Defaults to unset, and any number of operations can be requested at any time\&.
669 \fIReloadLimitIntervalSec=\fR
670 takes a value in seconds to configure the rate limit window, and
671 \fIReloadLimitBurst=\fR
672 takes a positive integer to configure the maximum allowed number of operations within the configured time window\&.
673 .sp
674 Added in version 253\&.
675 .RE
676 .PP
677 \fIEventLoopRateLimitIntervalSec=\fR, \fIEventLoopRateLimitBurst=\fR
678 .RS 4
679 Configures the rate limiting applied to the manager\*(Aqs main event loop\&. If the event loop iterates more than
680 \fIEventLoopRateLimitBurst=\fR
681 times within
682 \fIEventLoopRateLimitIntervalSec=\fR, event processing is briefly paused to prevent excessive CPU usage\&.
683 \fIEventLoopRateLimitIntervalSec=\fR
684 defaults to 1s\&.
685 \fIEventLoopRateLimitBurst=\fR
686 defaults to 50000\&. These settings can also be set on the kernel command line via
687 \fIsystemd\&.event_loop_ratelimit_interval_sec=\fR
688 and
689 \fIsystemd\&.event_loop_ratelimit_burst=\fR\&.
690 .sp
691 Added in version 261\&.
692 .RE
693 .PP
694 \fIMinimumUptimeSec=\fR
695 .RS 4
696 Specifies the minimum uptime for the system which has to be reached before a shutdown is executed\&. Defaults to 15s\&. This mechanism is introduced to avoid high frequency reboot loops, when technical failures trigger an automatic shutdown during the boot process\&. Each reboot cycle is delayed to the specified minimum time, giving the user a chance to review screen contents or otherwise interact with the device before the shutdown proceeds\&. The delay takes place during the very last phase of system shutdown, immediately before the
697 \fBreboot()\fR
698 system call is executed\&. If the system is already running for longer than the specified time, this setting has no effect\&. This logic is also skipped in container environments\&. Set to zero in order to disable this logic\&.
699 .sp
700 Added in version 261\&.
701 .RE
702 .SH "ENVIRONMENT"
703 .PP
704 \fIDefaultEnvironment=\fR
705 .RS 4
706 Configures environment variables passed to all executed processes\&. Takes a space\-separated list of variable assignments\&. See
707 \fBenviron\fR(7)
708 for details about environment variables\&. This environment block is internal, and changes are not reflected in the manager\*(Aqs
709 /proc/PID/environ\&.
710 .sp
711 Simple
712 "%"\-specifier expansion is supported, see below for a list of supported specifiers\&.
713 .sp
714 Example:
715 .sp
716 .if n \{\
717 .RS 4
718 .\}
719 .nf
720 DefaultEnvironment="VAR1=word1 word2" VAR2=word3 "VAR3=word 5 6"
721 .fi
722 .if n \{\
723 .RE
724 .\}
725 .sp
726 Sets three variables
727 "VAR1",
728 "VAR2",
729 "VAR3"\&.
730 .sp
731 Added in version 205\&.
732 .RE
733 .PP
734 \fIManagerEnvironment=\fR
735 .RS 4
736 Sets environment variables for the manager process itself\&. Takes a space\-separated list of variable assignment in the same format as
737 \fIDefaultEnvironment=\fR, see above\&. These variables are merged into the existing environment block of the manager process\&. In particular, in case of the system manager, this block includes variables set by the kernel based on the kernel command line, and in case of the user manager, the variables passed by the system manager\&. After those variables have been merged, they will persist until overridden, even if the manager is reloaded or reexecuted\&. In case of the user manager, these variables are also inherited by processes spawned by the manager\&. As with
738 \fIDefaultEnvironment=\fR, this environment block is internal, and changes are not reflected in the manager\*(Aqs
739 /proc/PID/environ\&.
740 .sp
741 Setting environment variables for the manager process may be useful to modify its behaviour\&. See
742 \m[blue]\fBKnown Environment Variables\fR\m[]\&\s-2\u[3]\d\s+2
743 for a description of some variables understood by
744 \fBsystemd\fR\&.
745 .sp
746 Simple
747 "%"\-specifier expansion is supported, see below for a list of supported specifiers\&.
748 .sp
749 Added in version 248\&.
750 .RE
751 .PP
752 \fIDefaultMemoryZSwapWriteback=\fR
753 .RS 4
754 Takes a boolean argument\&. Defaults to true if unspecified\&. This is used as a default for units which lack an explicit definition for
755 \fIMemoryZSwapWriteback=\fR\&. See
756 \fBsystemd.resource-control\fR(5)
757 for the details\&.
758 .sp
759 Added in version 261\&.
760 .RE
761 .SH "SPECIFIERS"
762 .PP
763 Specifiers may be used in the
764 \fIDefaultEnvironment=\fR
765 and
766 \fIManagerEnvironment=\fR
767 settings\&. The following expansions are understood:
768 .sp
769 .it 1 an-trap
770 .nr an-no-space-flag 1
771 .nr an-break-flag 1
772 .br
773 .B Table\ \&1.\ \&Specifiers available
774 .TS
775 allbox tab(:);
776 lB lB lB.
777 T{
778 Specifier
779 T}:T{
780 Meaning
781 T}:T{
782 Details
783 T}
784 .T&
785 l l l
786 l l l
787 l l l
788 l l l
789 l l l
790 l l l
791 l l l
792 l l l
793 l l l
794 l l l
795 l l l
796 l l l
797 l l l
798 l l l
799 l l l
800 l l l
801 l l l
802 l l l
803 l l l
804 l l l
805 l l l.
806 T{
807 "%a"
808 T}:T{
809 Architecture
810 T}:T{
811 A short string identifying the architecture of the local system\&. A string such as \fBx86\fR, \fBx86\-64\fR or \fBarm64\fR\&. See the architectures defined for \fIConditionArchitecture=\fR in \fBsystemd.unit\fR(5) for a full list\&.
812 T}
813 T{
814 "%A"
815 T}:T{
816 Operating system image version
817 T}:T{
818 The operating system image version identifier of the running system, as read from the \fIIMAGE_VERSION=\fR field of /etc/os\-release\&. If not set, resolves to an empty string\&. See \fBos-release\fR(5) for more information\&.
819 T}
820 T{
821 "%b"
822 T}:T{
823 Boot ID
824 T}:T{
825 The boot ID of the running system, formatted as string\&. See \fBrandom\fR(4) for more information\&.
826 T}
827 T{
828 "%B"
829 T}:T{
830 Operating system build ID
831 T}:T{
832 The operating system build identifier of the running system, as read from the \fIBUILD_ID=\fR field of /etc/os\-release\&. If not set, resolves to an empty string\&. See \fBos-release\fR(5) for more information\&.
833 T}
834 T{
835 "%H"
836 T}:T{
837 Host name
838 T}:T{
839 The hostname of the running system\&.
840 T}
841 T{
842 "%l"
843 T}:T{
844 Short host name
845 T}:T{
846 The hostname of the running system, truncated at the first dot to remove any domain component\&.
847 T}
848 T{
849 "%m"
850 T}:T{
851 Machine ID
852 T}:T{
853 The machine ID of the running system, formatted as string\&. See \fBmachine-id\fR(5) for more information\&.
854 T}
855 T{
856 "%M"
857 T}:T{
858 Operating system image identifier
859 T}:T{
860 The operating system image identifier of the running system, as read from the \fIIMAGE_ID=\fR field of /etc/os\-release\&. If not set, resolves to an empty string\&. See \fBos-release\fR(5) for more information\&.
861 T}
862 T{
863 "%o"
864 T}:T{
865 Operating system ID
866 T}:T{
867 The operating system identifier of the running system, as read from the \fIID=\fR field of /etc/os\-release\&. See \fBos-release\fR(5) for more information\&.
868 T}
869 T{
870 "%v"
871 T}:T{
872 Kernel release
873 T}:T{
874 Identical to \fBuname \-r\fR output\&.
875 T}
876 T{
877 "%w"
878 T}:T{
879 Operating system version ID
880 T}:T{
881 The operating system version identifier of the running system, as read from the \fIVERSION_ID=\fR field of /etc/os\-release\&. If not set, resolves to an empty string\&. See \fBos-release\fR(5) for more information\&.
882 T}
883 T{
884 "%W"
885 T}:T{
886 Operating system variant ID
887 T}:T{
888 The operating system variant identifier of the running system, as read from the \fIVARIANT_ID=\fR field of /etc/os\-release\&. If not set, resolves to an empty string\&. See \fBos-release\fR(5) for more information\&.
889 T}
890 T{
891 "%T"
892 T}:T{
893 Directory for temporary files
894 T}:T{
895 This is either /tmp or the path "$TMPDIR", "$TEMP" or "$TMP" are set to\&. (Note that the directory may be specified without a trailing slash\&.)
896 T}
897 T{
898 "%V"
899 T}:T{
900 Directory for larger and persistent temporary files
901 T}:T{
902 This is either /var/tmp or the path "$TMPDIR", "$TEMP" or "$TMP" are set to\&. (Note that the directory may be specified without a trailing slash\&.)
903 T}
904 T{
905 "%h"
906 T}:T{
907 User home directory
908 T}:T{
909 This is the home directory of the \fIuser running the service manager instance\fR\&.
910 T}
911 T{
912 "%u"
913 T}:T{
914 Username
915 T}:T{
916 This is the username of the \fIuser running the service manager instance\fR\&.
917 T}
918 T{
919 "%U"
920 T}:T{
921 User id
922 T}:T{
923 This is the user id of the \fIuser running the service manager instance\fR\&.
924 T}
925 T{
926 "%g"
927 T}:T{
928 Primary group
929 T}:T{
930 This is the primary group of the \fIuser running the service manager instance\fR\&.
931 T}
932 T{
933 "%G"
934 T}:T{
935 Primary group id
936 T}:T{
937 This is the primary group id of the \fIuser running the service manager instance\fR\&.
938 T}
939 T{
940 "%s"
941 T}:T{
942 User shell
943 T}:T{
944 This is the shell of the \fIuser running the service manager instance\fR\&.
945 T}
946 T{
947 "%%"
948 T}:T{
949 Single percent sign
950 T}:T{
951 Use "%%" in place of "%" to specify a single percent sign\&.
952 T}
953 .TE
954 .sp 1
955 .SH "HISTORY"
956 .PP
957 systemd 252
958 .RS 4
959 Option
960 \fIDefaultBlockIOAccounting=\fR
961 was deprecated\&. Please switch to the unified cgroup hierarchy\&.
962 .RE
963 .PP
964 systemd 258
965 .RS 4
966 \fIDefaultCPUAccounting=\fR
967 setting is deprecated, because CPU accounting is always available on the unified cgroup hierarchy and such setting has no effect\&.
968 .RE
969 .SH "SEE ALSO"
970 .PP
971 \fBsystemd\fR(1), \fBsystemd.directives\fR(7), \fBsystemd.exec\fR(5), \fBsystemd.service\fR(5), \fBenviron\fR(7), \fBcapabilities\fR(7)
972 .SH "NOTES"
973 .IP " 1." 4
974 ๐Ÿ’ฃ๐Ÿ’ฅ๐Ÿงจ๐Ÿ’ฅ๐Ÿ’ฅ๐Ÿ’ฃ Please note that those configuration files must be available at all times. If
975 /usr/local/
976 is a separate partition, it may not be available during early boot, and must not be used for configuration.
977 .IP " 2." 4
978 No New Privileges Flag
979 .RS 4
980 \%https://docs.kernel.org/userspace-api/no_new_privs.html
981 .RE
982 .IP " 3." 4
983 Known Environment Variables
984 .RS 4
985 \%https://systemd.io/ENVIRONMENT
986 .RE