Debian Codegraph @

upstream/opensuse-tumbleweed/man5/systemd-system.conf.5

raw
1 '\" t
2 .TH "SYSTEMD\-SYSTEM\&.CONF" "5" "" "systemd 260.1" "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 .SH "HARDWARE WATCHDOG"
345 .PP
346 \fIRuntimeWatchdogSec=\fR, \fIRebootWatchdogSec=\fR, \fIKExecWatchdogSec=\fR
347 .RS 4
348 Configure the hardware watchdog at runtime and at reboot\&. Takes a timeout value in seconds (or in other time units if suffixed with
349 "ms",
350 "min",
351 "h",
352 "d",
353 "w"), or the special strings
354 "off"
355 or
356 "default"\&. If set to
357 "off"
358 (alternatively:
359 "0") the watchdog logic is disabled: no watchdog device is opened, configured, or pinged\&. If set to the special string
360 "default"
361 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)\&.
362 .sp
363 If
364 \fIRuntimeWatchdogSec=\fR
365 is set to a non\-zero value, the watchdog hardware (/dev/watchdog0
366 or the path specified with
367 \fIWatchdogDevice=\fR
368 or the kernel option
369 \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\&.
370 .sp
371 \fIRebootWatchdogSec=\fR
372 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
373 \fIRebootWatchdogSec=\fR
374 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
375 systemd\-shutdown
376 binary, see system
377 \fBbootup\fR(7)
378 for details\&. During the first phase of the shutdown operation the system and service manager remains running and hence
379 \fIRuntimeWatchdogSec=\fR
380 is still honoured\&. In order to define a timeout on this first phase of system shutdown, configure
381 \fIJobTimeoutSec=\fR
382 and
383 \fIJobTimeoutAction=\fR
384 in the [Unit] section of the
385 shutdown\&.target
386 unit\&. By default,
387 \fIRuntimeWatchdogSec=\fR
388 defaults to 0 (off), and
389 \fIRebootWatchdogSec=\fR
390 to 10min\&.
391 .sp
392 \fIKExecWatchdogSec=\fR
393 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
394 \fIRuntimeWatchdogSec=\fR
395 is also enabled at the same time\&. For this reason it is recommended to enable
396 \fIKExecWatchdogSec=\fR
397 only if
398 \fIRuntimeWatchdogSec=\fR
399 is also enabled\&.
400 .sp
401 These settings have no effect if a hardware watchdog is not available\&.
402 .sp
403 Added in version 198\&.
404 .RE
405 .PP
406 \fIRuntimeWatchdogPreSec=\fR
407 .RS 4
408 Configure the hardware watchdog device pre\-timeout value\&. Takes a timeout value in seconds (or in other time units similar to
409 \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
410 \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
411 \fIRuntimeWatchdogPreSec=\fR
412 before the runtime watchdog timeout (set by
413 \fIRuntimeWatchdogSec=\fR)\&. For example, if the we have
414 \fIRuntimeWatchdogSec=30\fR
415 and
416 \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,
417 \fIRuntimeWatchdogPreSec=\fR
418 defaults to 0 (off)\&. The value set for
419 \fIRuntimeWatchdogPreSec=\fR
420 must be smaller than the timeout value for
421 \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\&.
422 .sp
423 Added in version 251\&.
424 .RE
425 .PP
426 \fIRuntimeWatchdogPreGovernor=\fR
427 .RS 4
428 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
429 /sys/class/watchdog/watchdog\fIX\fR/pretimeout_available_governors
430 file\&. Typically, available governor types are
431 \fInoop\fR
432 and
433 \fIpanic\fR\&. Availability, names and functionality might vary depending on the specific device driver in use\&. If the
434 pretimeout_available_governors
435 sysfs file is empty, the governor might be built as a kernel module and might need to be manually loaded (e\&.g\&.
436 \fIpretimeout_noop\&.ko\fR), or the watchdog device might not support pre\-timeouts\&.
437 .sp
438 Added in version 251\&.
439 .RE
440 .PP
441 \fIWatchdogDevice=\fR
442 .RS 4
443 Configure the hardware watchdog device that the runtime and shutdown watchdog timers will open and use\&. Defaults to
444 /dev/watchdog0\&. This setting has no effect if a hardware watchdog is not available\&.
445 .sp
446 Added in version 236\&.
447 .RE
448 .SH "SECURITY"
449 .PP
450 \fICapabilityBoundingSet=\fR
451 .RS 4
452 Controls which capabilities to include in the capability bounding set for PID 1 and its children\&. See
453 \fBcapabilities\fR(7)
454 for details\&. Takes a whitespace\-separated list of capability names as read by
455 \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
456 \fICapabilityBoundingSet=\fR
457 directive for units, but note that capabilities dropped for PID 1 cannot be regained in individual units, they are lost for good\&.
458 .sp
459 Added in version 198\&.
460 .RE
461 .PP
462 \fINoNewPrivileges=\fR
463 .RS 4
464 Takes a boolean argument\&. If true, ensures that PID 1 and all its children can never gain new privileges through
465 \fBexecve\fR(2)
466 (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
467 \m[blue]\fBNo New Privileges Flag\fR\m[]\&\s-2\u[2]\d\s+2\&.
468 .sp
469 Added in version 239\&.
470 .RE
471 .PP
472 \fIProtectSystem=\fR
473 .RS 4
474 Takes a boolean argument or the string
475 "auto"\&. If set to true this will remount
476 /usr/
477 read\-only\&. If set to
478 "auto"
479 (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
480 \fBsystemd.exec\fR(5)
481 for details: currently, the
482 "full"
483 or
484 "strict"
485 values are not supported\&.
486 .sp
487 Added in version 256\&.
488 .RE
489 .PP
490 \fISystemCallArchitectures=\fR
491 .RS 4
492 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
493 \fISystemCallArchitectures=\fR
494 setting of unit files, see
495 \fBsystemd.exec\fR(5)
496 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
497 "x86",
498 "x86\-64",
499 "x32",
500 "arm"
501 and the special identifier
502 "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
503 "native"
504 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\&.
505 .sp
506 Added in version 209\&.
507 .RE
508 .PP
509 \fIDefaultSmackProcessLabel=\fR
510 .RS 4
511 Takes a
512 \fBSMACK64\fR
513 security label as the argument\&. The process executed by a unit will be started under this label if
514 \fISmackProcessLabel=\fR
515 is not set in the unit\&. See
516 \fBsystemd.exec\fR(5)
517 for the details\&.
518 .sp
519 If the value is
520 "/", only labels specified with
521 \fISmackProcessLabel=\fR
522 are assigned and the compile\-time default is ignored\&.
523 .sp
524 Added in version 252\&.
525 .RE
526 .PP
527 \fIDefaultRestrictSUIDSGID=\fR
528 .RS 4
529 Takes a boolean argument\&. This is used as a default for units which lack an explicit definition for
530 \fIRestrictSUIDSGID=\fR\&. See
531 \fBsystemd.exec\fR(5)
532 for the details\&.
533 .sp
534 Added in version 258\&.
535 .RE
536 .SH "TIMEOUTS AND RATE LIMITS"
537 .PP
538 \fIDefaultTimeoutStartSec=\fR, \fIDefaultTimeoutStopSec=\fR, \fIDefaultTimeoutAbortSec=\fR, \fIDefaultRestartSec=\fR
539 .RS 4
540 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
541 \fITimeoutStartSec=\fR,
542 \fITimeoutStopSec=\fR,
543 \fITimeoutAbortSec=\fR
544 and
545 \fIRestartSec=\fR
546 (for services, see
547 \fBsystemd.service\fR(5)
548 for details on the per\-unit settings)\&. For non\-service units,
549 \fIDefaultTimeoutStartSec=\fR
550 sets the default
551 \fITimeoutSec=\fR
552 value\&.
553 .sp
554 \fIDefaultTimeoutStartSec=\fR
555 and
556 \fIDefaultTimeoutStopSec=\fR
557 default to 90 s in the system manager and 90 s in the user manager\&.
558 \fIDefaultTimeoutAbortSec=\fR
559 is not set by default so that all units fall back to
560 \fITimeoutStopSec=\fR\&.
561 \fIDefaultRestartSec=\fR
562 defaults to 100 ms\&.
563 .sp
564 Added in version 209\&.
565 .RE
566 .PP
567 \fIDefaultDeviceTimeoutSec=\fR
568 .RS 4
569 Configures the default timeout for waiting for devices\&. It can be changed per device via the
570 \fIx\-systemd\&.device\-timeout=\fR
571 option in
572 /etc/fstab
573 and
574 /etc/crypttab
575 (see
576 \fBsystemd.mount\fR(5),
577 \fBcrypttab\fR(5))\&. Defaults to 90 s in the system manager and 90 s in the user manager\&.
578 .sp
579 Added in version 252\&.
580 .RE
581 .PP
582 \fIDefaultStartLimitIntervalSec=\fR, \fIDefaultStartLimitBurst=\fR
583 .RS 4
584 Configure the default unit start rate limiting, as configured per\-service by
585 \fIStartLimitIntervalSec=\fR
586 and
587 \fIStartLimitBurst=\fR\&. See
588 \fBsystemd.service\fR(5)
589 for details on the per\-service settings\&.
590 \fIDefaultStartLimitIntervalSec=\fR
591 defaults to 10s\&.
592 \fIDefaultStartLimitBurst=\fR
593 defaults to 5\&.
594 .sp
595 Added in version 209\&.
596 .RE
597 .PP
598 \fIReloadLimitIntervalSec=\fR, \fIReloadLimitBurst=\fR
599 .RS 4
600 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\&.
601 \fIReloadLimitIntervalSec=\fR
602 takes a value in seconds to configure the rate limit window, and
603 \fIReloadLimitBurst=\fR
604 takes a positive integer to configure the maximum allowed number of operations within the configured time window\&.
605 .sp
606 Added in version 253\&.
607 .RE
608 .SH "ENVIRONMENT"
609 .PP
610 \fIDefaultEnvironment=\fR
611 .RS 4
612 Configures environment variables passed to all executed processes\&. Takes a space\-separated list of variable assignments\&. See
613 \fBenviron\fR(7)
614 for details about environment variables\&. This environment block is internal, and changes are not reflected in the manager\*(Aqs
615 /proc/PID/environ\&.
616 .sp
617 Simple
618 "%"\-specifier expansion is supported, see below for a list of supported specifiers\&.
619 .sp
620 Example:
621 .sp
622 .if n \{\
623 .RS 4
624 .\}
625 .nf
626 DefaultEnvironment="VAR1=word1 word2" VAR2=word3 "VAR3=word 5 6"
627 .fi
628 .if n \{\
629 .RE
630 .\}
631 .sp
632 Sets three variables
633 "VAR1",
634 "VAR2",
635 "VAR3"\&.
636 .sp
637 Added in version 205\&.
638 .RE
639 .PP
640 \fIManagerEnvironment=\fR
641 .RS 4
642 Sets environment variables for the manager process itself\&. Takes a space\-separated list of variable assignment in the same format as
643 \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
644 \fIDefaultEnvironment=\fR, this environment block is internal, and changes are not reflected in the manager\*(Aqs
645 /proc/PID/environ\&.
646 .sp
647 Setting environment variables for the manager process may be useful to modify its behaviour\&. See
648 \m[blue]\fBKnown Environment Variables\fR\m[]\&\s-2\u[3]\d\s+2
649 for a description of some variables understood by
650 \fBsystemd\fR\&.
651 .sp
652 Simple
653 "%"\-specifier expansion is supported, see below for a list of supported specifiers\&.
654 .sp
655 Added in version 248\&.
656 .RE
657 .SH "SPECIFIERS"
658 .PP
659 Specifiers may be used in the
660 \fIDefaultEnvironment=\fR
661 and
662 \fIManagerEnvironment=\fR
663 settings\&. The following expansions are understood:
664 .sp
665 .it 1 an-trap
666 .nr an-no-space-flag 1
667 .nr an-break-flag 1
668 .br
669 .B Table\ \&1.\ \&Specifiers available
670 .TS
671 allbox tab(:);
672 lB lB lB.
673 T{
674 Specifier
675 T}:T{
676 Meaning
677 T}:T{
678 Details
679 T}
680 .T&
681 l l l
682 l l l
683 l l l
684 l l l
685 l l l
686 l l l
687 l l l
688 l l l
689 l l l
690 l l l
691 l l l
692 l l l
693 l l l
694 l l l
695 l l l
696 l l l
697 l l l
698 l l l
699 l l l
700 l l l
701 l l l.
702 T{
703 "%a"
704 T}:T{
705 Architecture
706 T}:T{
707 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\&.
708 T}
709 T{
710 "%A"
711 T}:T{
712 Operating system image version
713 T}:T{
714 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\&.
715 T}
716 T{
717 "%b"
718 T}:T{
719 Boot ID
720 T}:T{
721 The boot ID of the running system, formatted as string\&. See \fBrandom\fR(4) for more information\&.
722 T}
723 T{
724 "%B"
725 T}:T{
726 Operating system build ID
727 T}:T{
728 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\&.
729 T}
730 T{
731 "%H"
732 T}:T{
733 Host name
734 T}:T{
735 The hostname of the running system\&.
736 T}
737 T{
738 "%l"
739 T}:T{
740 Short host name
741 T}:T{
742 The hostname of the running system, truncated at the first dot to remove any domain component\&.
743 T}
744 T{
745 "%m"
746 T}:T{
747 Machine ID
748 T}:T{
749 The machine ID of the running system, formatted as string\&. See \fBmachine-id\fR(5) for more information\&.
750 T}
751 T{
752 "%M"
753 T}:T{
754 Operating system image identifier
755 T}:T{
756 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\&.
757 T}
758 T{
759 "%o"
760 T}:T{
761 Operating system ID
762 T}:T{
763 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\&.
764 T}
765 T{
766 "%v"
767 T}:T{
768 Kernel release
769 T}:T{
770 Identical to \fBuname \-r\fR output\&.
771 T}
772 T{
773 "%w"
774 T}:T{
775 Operating system version ID
776 T}:T{
777 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\&.
778 T}
779 T{
780 "%W"
781 T}:T{
782 Operating system variant ID
783 T}:T{
784 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\&.
785 T}
786 T{
787 "%T"
788 T}:T{
789 Directory for temporary files
790 T}:T{
791 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\&.)
792 T}
793 T{
794 "%V"
795 T}:T{
796 Directory for larger and persistent temporary files
797 T}:T{
798 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\&.)
799 T}
800 T{
801 "%h"
802 T}:T{
803 User home directory
804 T}:T{
805 This is the home directory of the \fIuser running the service manager instance\fR\&.
806 T}
807 T{
808 "%u"
809 T}:T{
810 Username
811 T}:T{
812 This is the username of the \fIuser running the service manager instance\fR\&.
813 T}
814 T{
815 "%U"
816 T}:T{
817 User id
818 T}:T{
819 This is the user id of the \fIuser running the service manager instance\fR\&.
820 T}
821 T{
822 "%g"
823 T}:T{
824 Primary group
825 T}:T{
826 This is the primary group of the \fIuser running the service manager instance\fR\&.
827 T}
828 T{
829 "%G"
830 T}:T{
831 Primary group id
832 T}:T{
833 This is the primary group id of the \fIuser running the service manager instance\fR\&.
834 T}
835 T{
836 "%s"
837 T}:T{
838 User shell
839 T}:T{
840 This is the shell of the \fIuser running the service manager instance\fR\&.
841 T}
842 T{
843 "%%"
844 T}:T{
845 Single percent sign
846 T}:T{
847 Use "%%" in place of "%" to specify a single percent sign\&.
848 T}
849 .TE
850 .sp 1
851 .SH "HISTORY"
852 .PP
853 systemd 252
854 .RS 4
855 Option
856 \fIDefaultBlockIOAccounting=\fR
857 was deprecated\&. Please switch to the unified cgroup hierarchy\&.
858 .RE
859 .PP
860 systemd 258
861 .RS 4
862 \fIDefaultCPUAccounting=\fR
863 setting is deprecated, because CPU accounting is always available on the unified cgroup hierarchy and such setting has no effect\&.
864 .RE
865 .SH "SEE ALSO"
866 .PP
867 \fBsystemd\fR(1), \fBsystemd.directives\fR(7), \fBsystemd.exec\fR(5), \fBsystemd.service\fR(5), \fBenviron\fR(7), \fBcapabilities\fR(7)
868 .SH "NOTES"
869 .IP " 1." 4
870 ๐Ÿ’ฃ๐Ÿ’ฅ๐Ÿงจ๐Ÿ’ฅ๐Ÿ’ฅ๐Ÿ’ฃ Please note that those configuration files must be available at all times. If
871 /usr/local/
872 is a separate partition, it may not be available during early boot, and must not be used for configuration.
873 .IP " 2." 4
874 No New Privileges Flag
875 .RS 4
876 \%https://docs.kernel.org/userspace-api/no_new_privs.html
877 .RE
878 .IP " 3." 4
879 Known Environment Variables
880 .RS 4
881 \%https://systemd.io/ENVIRONMENT
882 .RE