Debian Codegraph @

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

raw
1 '\" t
2 .TH "SYSTEMD\-SYSTEM\&.CONF" "5" "" "systemd 257.13" "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 \fIDefaultCPUAccounting=\fR, \fIDefaultMemoryAccounting=\fR, \fIDefaultTasksAccounting=\fR, \fIDefaultIOAccounting=\fR, \fIDefaultIPAccounting=\fR
206 .RS 4
207 Configure the default resource accounting settings, as configured per\-unit by
208 \fICPUAccounting=\fR,
209 \fIMemoryAccounting=\fR,
210 \fITasksAccounting=\fR,
211 \fIIOAccounting=\fR
212 and
213 \fIIPAccounting=\fR\&. See
214 \fBsystemd.resource-control\fR(5)
215 for details on the per\-unit settings\&.
216 .sp
217 \fIDefaultCPUAccounting=\fR
218 defaults to yes when running on kernel โ‰ฅ4\&.15, and no on older versions\&.
219 \fIDefaultMemoryAccounting=\fR
220 defaults to yes\&.
221 \fIDefaultTasksAccounting=\fR
222 defaults to yes\&. The other settings default to no\&.
223 .sp
224 Added in version 211\&.
225 .RE
226 .PP
227 \fIDefaultTasksMax=\fR
228 .RS 4
229 Configure the default value for the per\-unit
230 \fITasksMax=\fR
231 setting\&. See
232 \fBsystemd.resource-control\fR(5)
233 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
234 \fIkernel\&.pid_max=\fR,
235 \fIkernel\&.threads\-max=\fR
236 and root cgroup
237 \fIpids\&.max\fR\&. Kernel has a default value for
238 \fIkernel\&.pid_max=\fR
239 and an algorithm of counting in case of more than 32 cores\&. For example, with the default
240 \fIkernel\&.pid_max=\fR,
241 \fIDefaultTasksMax=\fR
242 defaults to 4915, but might be greater in other systems or smaller in OS containers\&.
243 .sp
244 Added in version 228\&.
245 .RE
246 .PP
247 \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
248 .RS 4
249 These settings control various default resource limits for processes executed by units\&. See
250 \fBsetrlimit\fR(2)
251 for details\&. These settings may be overridden in individual units using the corresponding
252 \fILimitXXX=\fR
253 directives and they accept the same parameter syntax, see
254 \fBsystemd.exec\fR(5)
255 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\&.
256 .sp
257 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:
258 .sp
259 .RS 4
260 .ie n \{\
261 \h'-04'\(bu\h'+03'\c
262 .\}
263 .el \{\
264 .sp -1
265 .IP \(bu 2.3
266 .\}
267 \fIDefaultLimitNOFILE=\fR
268 defaults to 1024:524288\&.
269 .RE
270 .sp
271 .RS 4
272 .ie n \{\
273 \h'-04'\(bu\h'+03'\c
274 .\}
275 .el \{\
276 .sp -1
277 .IP \(bu 2.3
278 .\}
279 \fIDefaultLimitMEMLOCK=\fR
280 defaults to 8M\&.
281 .RE
282 .sp
283 .RS 4
284 .ie n \{\
285 \h'-04'\(bu\h'+03'\c
286 .\}
287 .el \{\
288 .sp -1
289 .IP \(bu 2.3
290 .\}
291 \fIDefaultLimitCORE=\fR
292 does not have a default but it is worth mentioning that
293 \fIRLIMIT_CORE\fR
294 is set to
295 "infinity"
296 by PID 1 which is inherited by its children\&.
297 .RE
298 .sp
299 Note that the service manager internally in PID 1 bumps
300 \fIRLIMIT_NOFILE\fR
301 and
302 \fIRLIMIT_MEMLOCK\fR
303 to higher values, however the limit is reverted to the mentioned defaults for all child processes forked off\&.
304 .sp
305 Added in version 198\&.
306 .RE
307 .PP
308 \fIDefaultOOMPolicy=\fR
309 .RS 4
310 Configure the default policy for reacting to processes being killed by the Linux Out\-Of\-Memory (OOM) killer or
311 \fBsystemd\-oomd\fR\&. This may be used to pick a global default for the per\-unit
312 \fIOOMPolicy=\fR
313 setting\&. See
314 \fBsystemd.service\fR(5)
315 for details\&. Note that this default is not used for services that have
316 \fIDelegate=\fR
317 turned on\&.
318 .sp
319 Added in version 243\&.
320 .RE
321 .PP
322 \fIDefaultOOMScoreAdjust=\fR
323 .RS 4
324 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
325 \fIOOMScoreAdjust=\fR
326 setting\&. See
327 \fBsystemd.exec\fR(5)
328 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\&.
329 .sp
330 Added in version 250\&.
331 .RE
332 .PP
333 \fIDefaultMemoryPressureWatch=\fR, \fIDefaultMemoryPressureThresholdSec=\fR
334 .RS 4
335 Configures the default settings for the per\-unit
336 \fIMemoryPressureWatch=\fR
337 and
338 \fIMemoryPressureThresholdSec=\fR
339 settings\&. See
340 \fBsystemd.resource-control\fR(5)
341 for details\&. Defaults to
342 "auto"
343 and
344 "200ms", respectively\&. This also sets the memory pressure monitoring threshold for the service manager itself\&.
345 .sp
346 Added in version 254\&.
347 .RE
348 .SH "HARDWARE WATCHDOG"
349 .PP
350 \fIRuntimeWatchdogSec=\fR, \fIRebootWatchdogSec=\fR, \fIKExecWatchdogSec=\fR
351 .RS 4
352 Configure the hardware watchdog at runtime and at reboot\&. Takes a timeout value in seconds (or in other time units if suffixed with
353 "ms",
354 "min",
355 "h",
356 "d",
357 "w"), or the special strings
358 "off"
359 or
360 "default"\&. If set to
361 "off"
362 (alternatively:
363 "0") the watchdog logic is disabled: no watchdog device is opened, configured, or pinged\&. If set to the special string
364 "default"
365 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)\&.
366 .sp
367 If
368 \fIRuntimeWatchdogSec=\fR
369 is set to a non\-zero value, the watchdog hardware (/dev/watchdog0
370 or the path specified with
371 \fIWatchdogDevice=\fR
372 or the kernel option
373 \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\&.
374 .sp
375 \fIRebootWatchdogSec=\fR
376 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
377 \fIRebootWatchdogSec=\fR
378 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
379 systemd\-shutdown
380 binary, see system
381 \fBbootup\fR(7)
382 for details\&. During the first phase of the shutdown operation the system and service manager remains running and hence
383 \fIRuntimeWatchdogSec=\fR
384 is still honoured\&. In order to define a timeout on this first phase of system shutdown, configure
385 \fIJobTimeoutSec=\fR
386 and
387 \fIJobTimeoutAction=\fR
388 in the [Unit] section of the
389 shutdown\&.target
390 unit\&. By default,
391 \fIRuntimeWatchdogSec=\fR
392 defaults to 0 (off), and
393 \fIRebootWatchdogSec=\fR
394 to 10min\&.
395 .sp
396 \fIKExecWatchdogSec=\fR
397 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
398 \fIRuntimeWatchdogSec=\fR
399 is also enabled at the same time\&. For this reason it is recommended to enable
400 \fIKExecWatchdogSec=\fR
401 only if
402 \fIRuntimeWatchdogSec=\fR
403 is also enabled\&.
404 .sp
405 These settings have no effect if a hardware watchdog is not available\&.
406 .sp
407 Added in version 198\&.
408 .RE
409 .PP
410 \fIRuntimeWatchdogPreSec=\fR
411 .RS 4
412 Configure the hardware watchdog device pre\-timeout value\&. Takes a timeout value in seconds (or in other time units similar to
413 \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
414 \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
415 \fIRuntimeWatchdogPreSec=\fR
416 before the runtime watchdog timeout (set by
417 \fIRuntimeWatchdogSec=\fR)\&. For example, if the we have
418 \fIRuntimeWatchdogSec=30\fR
419 and
420 \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,
421 \fIRuntimeWatchdogPreSec=\fR
422 defaults to 0 (off)\&. The value set for
423 \fIRuntimeWatchdogPreSec=\fR
424 must be smaller than the timeout value for
425 \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\&.
426 .sp
427 Added in version 251\&.
428 .RE
429 .PP
430 \fIRuntimeWatchdogPreGovernor=\fR
431 .RS 4
432 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
433 /sys/class/watchdog/watchdog\fIX\fR/pretimeout_available_governors
434 file\&. Typically, available governor types are
435 \fInoop\fR
436 and
437 \fIpanic\fR\&. Availability, names and functionality might vary depending on the specific device driver in use\&. If the
438 pretimeout_available_governors
439 sysfs file is empty, the governor might be built as a kernel module and might need to be manually loaded (e\&.g\&.
440 \fIpretimeout_noop\&.ko\fR), or the watchdog device might not support pre\-timeouts\&.
441 .sp
442 Added in version 251\&.
443 .RE
444 .PP
445 \fIWatchdogDevice=\fR
446 .RS 4
447 Configure the hardware watchdog device that the runtime and shutdown watchdog timers will open and use\&. Defaults to
448 /dev/watchdog0\&. This setting has no effect if a hardware watchdog is not available\&.
449 .sp
450 Added in version 236\&.
451 .RE
452 .SH "SECURITY"
453 .PP
454 \fICapabilityBoundingSet=\fR
455 .RS 4
456 Controls which capabilities to include in the capability bounding set for PID 1 and its children\&. See
457 \fBcapabilities\fR(7)
458 for details\&. Takes a whitespace\-separated list of capability names as read by
459 \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
460 \fICapabilityBoundingSet=\fR
461 directive for units, but note that capabilities dropped for PID 1 cannot be regained in individual units, they are lost for good\&.
462 .sp
463 Added in version 198\&.
464 .RE
465 .PP
466 \fINoNewPrivileges=\fR
467 .RS 4
468 Takes a boolean argument\&. If true, ensures that PID 1 and all its children can never gain new privileges through
469 \fBexecve\fR(2)
470 (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
471 \m[blue]\fBNo New Privileges Flag\fR\m[]\&\s-2\u[2]\d\s+2\&.
472 .sp
473 Added in version 239\&.
474 .RE
475 .PP
476 \fIProtectSystem=\fR
477 .RS 4
478 Takes a boolean argument or the string
479 "auto"\&. If set to true this will remount
480 /usr/
481 read\-only\&. If set to
482 "auto"
483 (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
484 \fBsystemd.exec\fR(5)
485 for details: currently, the
486 "full"
487 or
488 "strict"
489 values are not supported\&.
490 .sp
491 Added in version 256\&.
492 .RE
493 .PP
494 \fISystemCallArchitectures=\fR
495 .RS 4
496 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
497 \fISystemCallArchitectures=\fR
498 setting of unit files, see
499 \fBsystemd.exec\fR(5)
500 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
501 "x86",
502 "x86\-64",
503 "x32",
504 "arm"
505 and the special identifier
506 "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
507 "native"
508 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\&.
509 .sp
510 Added in version 209\&.
511 .RE
512 .PP
513 \fIDefaultSmackProcessLabel=\fR
514 .RS 4
515 Takes a
516 \fBSMACK64\fR
517 security label as the argument\&. The process executed by a unit will be started under this label if
518 \fISmackProcessLabel=\fR
519 is not set in the unit\&. See
520 \fBsystemd.exec\fR(5)
521 for the details\&.
522 .sp
523 If the value is
524 "/", only labels specified with
525 \fISmackProcessLabel=\fR
526 are assigned and the compile\-time default is ignored\&.
527 .sp
528 Added in version 252\&.
529 .RE
530 .SH "TIMEOUTS AND RATE LIMITS"
531 .PP
532 \fIDefaultTimeoutStartSec=\fR, \fIDefaultTimeoutStopSec=\fR, \fIDefaultTimeoutAbortSec=\fR, \fIDefaultRestartSec=\fR
533 .RS 4
534 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
535 \fITimeoutStartSec=\fR,
536 \fITimeoutStopSec=\fR,
537 \fITimeoutAbortSec=\fR
538 and
539 \fIRestartSec=\fR
540 (for services, see
541 \fBsystemd.service\fR(5)
542 for details on the per\-unit settings)\&. For non\-service units,
543 \fIDefaultTimeoutStartSec=\fR
544 sets the default
545 \fITimeoutSec=\fR
546 value\&.
547 .sp
548 \fIDefaultTimeoutStartSec=\fR
549 and
550 \fIDefaultTimeoutStopSec=\fR
551 default to 90 s in the system manager and 90 s in the user manager\&.
552 \fIDefaultTimeoutAbortSec=\fR
553 is not set by default so that all units fall back to
554 \fITimeoutStopSec=\fR\&.
555 \fIDefaultRestartSec=\fR
556 defaults to 100 ms\&.
557 .sp
558 Added in version 209\&.
559 .RE
560 .PP
561 \fIDefaultDeviceTimeoutSec=\fR
562 .RS 4
563 Configures the default timeout for waiting for devices\&. It can be changed per device via the
564 \fIx\-systemd\&.device\-timeout=\fR
565 option in
566 /etc/fstab
567 and
568 /etc/crypttab
569 (see
570 \fBsystemd.mount\fR(5),
571 \fBcrypttab\fR(5))\&. Defaults to 90 s in the system manager and 90 s in the user manager\&.
572 .sp
573 Added in version 252\&.
574 .RE
575 .PP
576 \fIDefaultStartLimitIntervalSec=\fR, \fIDefaultStartLimitBurst=\fR
577 .RS 4
578 Configure the default unit start rate limiting, as configured per\-service by
579 \fIStartLimitIntervalSec=\fR
580 and
581 \fIStartLimitBurst=\fR\&. See
582 \fBsystemd.service\fR(5)
583 for details on the per\-service settings\&.
584 \fIDefaultStartLimitIntervalSec=\fR
585 defaults to 10s\&.
586 \fIDefaultStartLimitBurst=\fR
587 defaults to 5\&.
588 .sp
589 Added in version 209\&.
590 .RE
591 .PP
592 \fIReloadLimitIntervalSec=\fR, \fIReloadLimitBurst=\fR
593 .RS 4
594 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\&.
595 \fIReloadLimitIntervalSec=\fR
596 takes a value in seconds to configure the rate limit window, and
597 \fIReloadLimitBurst=\fR
598 takes a positive integer to configure the maximum allowed number of operations within the configured time window\&.
599 .sp
600 Added in version 253\&.
601 .RE
602 .SH "ENVIRONMENT"
603 .PP
604 \fIDefaultEnvironment=\fR
605 .RS 4
606 Configures environment variables passed to all executed processes\&. Takes a space\-separated list of variable assignments\&. See
607 \fBenviron\fR(7)
608 for details about environment variables\&. This environment block is internal, and changes are not reflected in the manager\*(Aqs
609 /proc/PID/environ\&.
610 .sp
611 Simple
612 "%"\-specifier expansion is supported, see below for a list of supported specifiers\&.
613 .sp
614 Example:
615 .sp
616 .if n \{\
617 .RS 4
618 .\}
619 .nf
620 DefaultEnvironment="VAR1=word1 word2" VAR2=word3 "VAR3=word 5 6"
621 .fi
622 .if n \{\
623 .RE
624 .\}
625 .sp
626 Sets three variables
627 "VAR1",
628 "VAR2",
629 "VAR3"\&.
630 .sp
631 Added in version 205\&.
632 .RE
633 .PP
634 \fIManagerEnvironment=\fR
635 .RS 4
636 Sets environment variables for the manager process itself\&. Takes a space\-separated list of variable assignment in the same format as
637 \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 overriden, 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
638 \fIDefaultEnvironment=\fR, this environment block is internal, and changes are not reflected in the manager\*(Aqs
639 /proc/PID/environ\&.
640 .sp
641 Setting environment variables for the manager process may be useful to modify its behaviour\&. See
642 \m[blue]\fBKnown Environment Variables\fR\m[]\&\s-2\u[3]\d\s+2
643 for a description of some variables understood by
644 \fBsystemd\fR\&.
645 .sp
646 Simple
647 "%"\-specifier expansion is supported, see below for a list of supported specifiers\&.
648 .sp
649 Added in version 248\&.
650 .RE
651 .SH "SPECIFIERS"
652 .PP
653 Specifiers may be used in the
654 \fIDefaultEnvironment=\fR
655 and
656 \fIManagerEnvironment=\fR
657 settings\&. The following expansions are understood:
658 .sp
659 .it 1 an-trap
660 .nr an-no-space-flag 1
661 .nr an-break-flag 1
662 .br
663 .B Table\ \&1.\ \&Specifiers available
664 .TS
665 allbox tab(:);
666 lB lB lB.
667 T{
668 Specifier
669 T}:T{
670 Meaning
671 T}:T{
672 Details
673 T}
674 .T&
675 l l l
676 l l l
677 l l l
678 l l l
679 l l l
680 l l l
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 T{
697 "%a"
698 T}:T{
699 Architecture
700 T}:T{
701 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\&.
702 T}
703 T{
704 "%A"
705 T}:T{
706 Operating system image version
707 T}:T{
708 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\&.
709 T}
710 T{
711 "%b"
712 T}:T{
713 Boot ID
714 T}:T{
715 The boot ID of the running system, formatted as string\&. See \fBrandom\fR(4) for more information\&.
716 T}
717 T{
718 "%B"
719 T}:T{
720 Operating system build ID
721 T}:T{
722 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\&.
723 T}
724 T{
725 "%H"
726 T}:T{
727 Host name
728 T}:T{
729 The hostname of the running system\&.
730 T}
731 T{
732 "%l"
733 T}:T{
734 Short host name
735 T}:T{
736 The hostname of the running system, truncated at the first dot to remove any domain component\&.
737 T}
738 T{
739 "%m"
740 T}:T{
741 Machine ID
742 T}:T{
743 The machine ID of the running system, formatted as string\&. See \fBmachine-id\fR(5) for more information\&.
744 T}
745 T{
746 "%M"
747 T}:T{
748 Operating system image identifier
749 T}:T{
750 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\&.
751 T}
752 T{
753 "%o"
754 T}:T{
755 Operating system ID
756 T}:T{
757 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\&.
758 T}
759 T{
760 "%v"
761 T}:T{
762 Kernel release
763 T}:T{
764 Identical to \fBuname \-r\fR output\&.
765 T}
766 T{
767 "%w"
768 T}:T{
769 Operating system version ID
770 T}:T{
771 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\&.
772 T}
773 T{
774 "%W"
775 T}:T{
776 Operating system variant ID
777 T}:T{
778 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\&.
779 T}
780 T{
781 "%T"
782 T}:T{
783 Directory for temporary files
784 T}:T{
785 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\&.)
786 T}
787 T{
788 "%V"
789 T}:T{
790 Directory for larger and persistent temporary files
791 T}:T{
792 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\&.)
793 T}
794 T{
795 "%h"
796 T}:T{
797 User home directory
798 T}:T{
799 This is the home directory of the \fIuser running the service manager instance\fR\&.
800 T}
801 T{
802 "%u"
803 T}:T{
804 Username
805 T}:T{
806 This is the username of the \fIuser running the service manager instance\fR\&.
807 T}
808 T{
809 "%U"
810 T}:T{
811 User id
812 T}:T{
813 This is the user id of the \fIuser running the service manager instance\fR\&.
814 T}
815 T{
816 "%g"
817 T}:T{
818 Primary group
819 T}:T{
820 This is the primary group of the \fIuser running the service manager instance\fR\&.
821 T}
822 T{
823 "%G"
824 T}:T{
825 Primary group id
826 T}:T{
827 This is the primary group id of the \fIuser running the service manager instance\fR\&.
828 T}
829 T{
830 "%s"
831 T}:T{
832 User shell
833 T}:T{
834 This is the shell of the \fIuser running the service manager instance\fR\&.
835 T}
836 T{
837 "%%"
838 T}:T{
839 Single percent sign
840 T}:T{
841 Use "%%" in place of "%" to specify a single percent sign\&.
842 T}
843 .TE
844 .sp 1
845 .SH "HISTORY"
846 .PP
847 systemd 252
848 .RS 4
849 Option
850 \fIDefaultBlockIOAccounting=\fR
851 was deprecated\&. Please switch to the unified cgroup hierarchy\&.
852 .sp
853 Added in version 252\&.
854 .RE
855 .SH "SEE ALSO"
856 .PP
857 \fBsystemd\fR(1), \fBsystemd.directives\fR(7), \fBsystemd.exec\fR(5), \fBsystemd.service\fR(5), \fBenviron\fR(7), \fBcapabilities\fR(7)
858 .SH "NOTES"
859 .IP " 1." 4
860 ๐Ÿ’ฃ๐Ÿ’ฅ๐Ÿงจ๐Ÿ’ฅ๐Ÿ’ฅ๐Ÿ’ฃ Please note that those configuration files must be available at all times. If
861 /usr/local/
862 is a separate partition, it may not be available during early boot, and must not be used for configuration.
863 .IP " 2." 4
864 No New Privileges Flag
865 .RS 4
866 \%https://docs.kernel.org/userspace-api/no_new_privs.html
867 .RE
868 .IP " 3." 4
869 Known Environment Variables
870 .RS 4
871 \%https://systemd.io/ENVIRONMENT
872 .RE