1SYSTEMD-SYSTEM.CONF(5)        systemd-system.conf       SYSTEMD-SYSTEM.CONF(5)
2
3
4

NAME

6       systemd-system.conf, system.conf.d, systemd-user.conf, user.conf.d -
7       System and session service manager configuration files
8

SYNOPSIS

10       /etc/systemd/system.conf, /etc/systemd/system.conf.d/*.conf,
11       /run/systemd/system.conf.d/*.conf,
12       /usr/lib/systemd/system.conf.d/*.conf
13
14       ~/.config/systemd/user.conf, /etc/systemd/user.conf,
15       /etc/systemd/user.conf.d/*.conf, /run/systemd/user.conf.d/*.conf,
16       /usr/lib/systemd/user.conf.d/*.conf
17

DESCRIPTION

19       When run as a system instance, systemd interprets the configuration
20       file system.conf and the files in system.conf.d directories; when run
21       as a user instance, it interprets the configuration file user.conf
22       (either in the home directory of the user, or if not found, under
23       /etc/systemd/) and the files in user.conf.d directories. These
24       configuration files contain a few settings controlling basic manager
25       operations.
26
27       See systemd.syntax(7) for a general description of the syntax.
28

CONFIGURATION DIRECTORIES AND PRECEDENCE

30       The default configuration is set during compilation, so configuration
31       is only needed when it is necessary to deviate from those defaults.
32       Initially, the main configuration file in /etc/systemd/ contains
33       commented out entries showing the defaults as a guide to the
34       administrator. Local overrides can be created by editing this file or
35       by creating drop-ins, as described below. Using drop-ins for local
36       configuration is recommended over modifications to the main
37       configuration file.
38
39       In addition to the "main" configuration file, drop-in configuration
40       snippets are read from /usr/lib/systemd/*.conf.d/,
41       /usr/local/lib/systemd/*.conf.d/, and /etc/systemd/*.conf.d/. Those
42       drop-ins have higher precedence and override the main configuration
43       file. Files in the *.conf.d/ configuration subdirectories are sorted by
44       their filename in lexicographic order, regardless of in which of the
45       subdirectories they reside. When multiple files specify the same
46       option, for options which accept just a single value, the entry in the
47       file sorted last takes precedence, and for options which accept a list
48       of values, entries are collected as they occur in the sorted files.
49
50       When packages need to customize the configuration, they can install
51       drop-ins under /usr/. Files in /etc/ are reserved for the local
52       administrator, who may use this logic to override the configuration
53       files installed by vendor packages. Drop-ins have to be used to
54       override package drop-ins, since the main configuration file has lower
55       precedence. It is recommended to prefix all filenames in those
56       subdirectories with a two-digit number and a dash, to simplify the
57       ordering of the files.
58
59       To disable a configuration file supplied by the vendor, the recommended
60       way is to place a symlink to /dev/null in the configuration directory
61       in /etc/, with the same filename as the vendor configuration file.
62

OPTIONS

64       All options are configured in the [Manager] section:
65
66       LogColor=, LogLevel=, LogLocation=, LogTarget=, LogTime=, DumpCore=yes,
67       CrashChangeVT=no, CrashShell=no, CrashReboot=no, ShowStatus=yes,
68       DefaultStandardOutput=journal, DefaultStandardError=inherit
69           Configures various parameters of basic manager operation. These
70           options may be overridden by the respective process and kernel
71           command line arguments. See systemd(1) for details.
72
73       CtrlAltDelBurstAction=
74           Defines what action will be performed if user presses
75           Ctrl-Alt-Delete more than 7 times in 2s. Can be set to
76           "reboot-force", "poweroff-force", "reboot-immediate",
77           "poweroff-immediate" or disabled with "none". Defaults to
78           "reboot-force".
79
80       CPUAffinity=
81           Configures the CPU affinity for the service manager as well as the
82           default CPU affinity for all forked off processes. Takes a list of
83           CPU indices or ranges separated by either whitespace or commas. CPU
84           ranges are specified by the lower and upper CPU indices separated
85           by a dash. This option may be specified more than once, in which
86           case the specified CPU affinity masks are merged. If the empty
87           string is assigned, the mask is reset, all assignments prior to
88           this will have no effect. Individual services may override the CPU
89           affinity for their processes with the CPUAffinity= setting in unit
90           files, see systemd.exec(5).
91
92       NUMAPolicy=
93           Configures the NUMA memory policy for the service manager and the
94           default NUMA memory policy for all forked off processes. Individual
95           services may override the default policy with the NUMAPolicy=
96           setting in unit files, see systemd.exec(5).
97
98       NUMAMask=
99           Configures the NUMA node mask that will be associated with the
100           selected NUMA policy. Note that default and local NUMA policies
101           don't require explicit NUMA node mask and value of the option can
102           be empty. Similarly to NUMAPolicy=, value can be overridden by
103           individual services in unit files, see systemd.exec(5).
104
105       RuntimeWatchdogSec=, RebootWatchdogSec=, KExecWatchdogSec=
106           Configure the hardware watchdog at runtime and at reboot. Takes a
107           timeout value in seconds (or in other time units if suffixed with
108           "ms", "min", "h", "d", "w"), or the special strings "off" or
109           "default". If set to "off" (alternatively: "0") the watchdog logic
110           is disabled: no watchdog device is opened, configured, or pinged.
111           If set to the special string "default" the watchdog is opened and
112           pinged in regular intervals, but the timeout is not changed from
113           the default. If set to any other time value the watchdog timeout is
114           configured to the specified value (or a value close to it,
115           depending on hardware capabilities).
116
117           If RuntimeWatchdogSec= is set to a non-zero value, the watchdog
118           hardware (/dev/watchdog0 or the path specified with WatchdogDevice=
119           or the kernel option systemd.watchdog-device=) will be programmed
120           to automatically reboot the system if it is not contacted within
121           the specified timeout interval. The system manager will ensure to
122           contact it at least once in half the specified timeout interval.
123           This feature requires a hardware watchdog device to be present, as
124           it is commonly the case in embedded and server systems. Not all
125           hardware watchdogs allow configuration of all possible reboot
126           timeout values, in which case the closest available timeout is
127           picked.
128
129           RebootWatchdogSec= may be used to configure the hardware watchdog
130           when the system is asked to reboot. It works as a safety net to
131           ensure that the reboot takes place even if a clean reboot attempt
132           times out. Note that the RebootWatchdogSec= timeout applies only to
133           the second phase of the reboot, i.e. after all regular services are
134           already terminated, and after the system and service manager
135           process (PID 1) got replaced by the systemd-shutdown binary, see
136           system bootup(7) for details. During the first phase of the
137           shutdown operation the system and service manager remains running
138           and hence RuntimeWatchdogSec= is still honoured. In order to define
139           a timeout on this first phase of system shutdown, configure
140           JobTimeoutSec= and JobTimeoutAction= in the [Unit] section of the
141           shutdown.target unit. By default RuntimeWatchdogSec= defaults to 0
142           (off), and RebootWatchdogSec= to 10min.
143
144           KExecWatchdogSec= may be used to additionally enable the watchdog
145           when kexec is being executed rather than when rebooting. Note that
146           if the kernel does not reset the watchdog on kexec (depending on
147           the specific hardware and/or driver), in this case the watchdog
148           might not get disabled after kexec succeeds and thus the system
149           might get rebooted, unless RuntimeWatchdogSec= is also enabled at
150           the same time. For this reason it is recommended to enable
151           KExecWatchdogSec= only if RuntimeWatchdogSec= is also enabled.
152
153           These settings have no effect if a hardware watchdog is not
154           available.
155
156       RuntimeWatchdogPreSec=
157           Configure the hardware watchdog device pre-timeout value. Takes a
158           timeout value in seconds (or in other time units similar to
159           RuntimeWatchdogSec=). A watchdog pre-timeout is a notification
160           generated by the watchdog before the watchdog reset might occur in
161           the event the watchdog has not been serviced. This notification is
162           handled by the kernel and can be configured to take an action (i.e.
163           generate a kernel panic) using RuntimeWatchdogPreGovernor=. Not all
164           watchdog hardware or drivers support generating a pre-timeout and
165           depending on the state of the system, the kernel may be unable to
166           take the configured action before the watchdog reboot. The watchdog
167           will be configured to generate the pre-timeout event at the amount
168           of time specified by RuntimeWatchdogPreSec= before the runtime
169           watchdog timeout (set by RuntimeWatchdogSec=). For example, if the
170           we have RuntimeWatchdogSec=30 and RuntimeWatchdogPreSec=10, then
171           the pre-timeout event will occur if the watchdog has not pinged for
172           20s (10s before the watchdog would fire). By default,
173           RuntimeWatchdogPreSec= defaults to 0 (off). The value set for
174           RuntimeWatchdogPreSec= must be smaller than the timeout value for
175           RuntimeWatchdogSec=. This setting has no effect if a hardware
176           watchdog is not available or the hardware watchdog does not support
177           a pre-timeout and will be ignored by the kernel if the setting is
178           greater than the actual watchdog timeout.
179
180       RuntimeWatchdogPreGovernor=
181           Configure the action taken by the hardware watchdog device when the
182           pre-timeout expires. The default action for the pre-timeout event
183           depends on the kernel configuration, but it is usually to log a
184           kernel message. For a list of valid actions available for a given
185           watchdog device, check the content of the
186           /sys/class/watchdog/watchdogX/pretimeout_available_governors file.
187           Typically, available governor types are noop and panic.
188           Availability, names and functionality might vary depending on the
189           specific device driver in use. If the
190           pretimeout_available_governors sysfs file is empty, the governor
191           might be built as a kernel module and might need to be manually
192           loaded (e.g.  pretimeout_noop.ko), or the watchdog device might not
193           support pre-timeouts.
194
195       WatchdogDevice=
196           Configure the hardware watchdog device that the runtime and
197           shutdown watchdog timers will open and use. Defaults to
198           /dev/watchdog0. This setting has no effect if a hardware watchdog
199           is not available.
200
201       CapabilityBoundingSet=
202           Controls which capabilities to include in the capability bounding
203           set for PID 1 and its children. See capabilities(7) for details.
204           Takes a whitespace-separated list of capability names as read by
205           cap_from_name(3). Capabilities listed will be included in the
206           bounding set, all others are removed. If the list of capabilities
207           is prefixed with ~, all but the listed capabilities will be
208           included, the effect of the assignment inverted. Note that this
209           option also affects the respective capabilities in the effective,
210           permitted and inheritable capability sets. The capability bounding
211           set may also be individually configured for units using the
212           CapabilityBoundingSet= directive for units, but note that
213           capabilities dropped for PID 1 cannot be regained in individual
214           units, they are lost for good.
215
216       NoNewPrivileges=
217           Takes a boolean argument. If true, ensures that PID 1 and all its
218           children can never gain new privileges through execve(2) (e.g. via
219           setuid or setgid bits, or filesystem capabilities). Defaults to
220           false. General purpose distributions commonly rely on executables
221           with setuid or setgid bits and will thus not function properly with
222           this option enabled. Individual units cannot disable this option.
223           Also see No New Privileges Flag[1].
224
225       SystemCallArchitectures=
226           Takes a space-separated list of architecture identifiers. Selects
227           from which architectures system calls may be invoked on this
228           system. This may be used as an effective way to disable invocation
229           of non-native binaries system-wide, for example to prohibit
230           execution of 32-bit x86 binaries on 64-bit x86-64 systems. This
231           option operates system-wide, and acts similar to the
232           SystemCallArchitectures= setting of unit files, see systemd.exec(5)
233           for details. This setting defaults to the empty list, in which case
234           no filtering of system calls based on architecture is applied.
235           Known architecture identifiers are "x86", "x86-64", "x32", "arm"
236           and the special identifier "native". The latter implicitly maps to
237           the native architecture of the system (or more specifically, the
238           architecture the system manager was compiled for). Set this setting
239           to "native" to prohibit execution of any non-native binaries. When
240           a binary executes a system call of an architecture that is not
241           listed in this setting, it will be immediately terminated with the
242           SIGSYS signal.
243
244       TimerSlackNSec=
245           Sets the timer slack in nanoseconds for PID 1, which is inherited
246           by all executed processes, unless overridden individually, for
247           example with the TimerSlackNSec= setting in service units (for
248           details see systemd.exec(5)). The timer slack controls the accuracy
249           of wake-ups triggered by system timers. See prctl(2) for more
250           information. Note that in contrast to most other time span
251           definitions this parameter takes an integer value in nano-seconds
252           if no unit is specified. The usual time units are understood too.
253
254       StatusUnitFormat=
255           Takes name, description or combined as the value. If name, the
256           system manager will use unit names in status messages (e.g.
257           "systemd-journald.service"), instead of the longer and more
258           informative descriptions set with Description= (e.g.  "Journal
259           Logging Service"). If combined, the system manager will use both
260           unit names and descriptions in status messages (e.g.
261           "systemd-journald.service - Journal Logging Service").
262
263           See systemd.unit(5) for details about unit names and Description=.
264
265       DefaultTimerAccuracySec=
266           Sets the default accuracy of timer units. This controls the global
267           default for the AccuracySec= setting of timer units, see
268           systemd.timer(5) for details.  AccuracySec= set in individual units
269           override the global default for the specific unit. Defaults to
270           1min. Note that the accuracy of timer units is also affected by the
271           configured timer slack for PID 1, see TimerSlackNSec= above.
272
273       DefaultTimeoutStartSec=, DefaultTimeoutStopSec=,
274       DefaultTimeoutAbortSec=, DefaultRestartSec=
275           Configures the default timeouts for starting, stopping and aborting
276           of units, as well as the default time to sleep between automatic
277           restarts of units, as configured per-unit in TimeoutStartSec=,
278           TimeoutStopSec=, TimeoutAbortSec= and RestartSec= (for services,
279           see systemd.service(5) for details on the per-unit settings).
280           Disabled by default, when service with Type=oneshot is used. For
281           non-service units, DefaultTimeoutStartSec= sets the default
282           TimeoutSec= value.  DefaultTimeoutStartSec= and
283           DefaultTimeoutStopSec= default to 90s.  DefaultTimeoutAbortSec= is
284           not set by default so that all units fall back to TimeoutStopSec=.
285           DefaultRestartSec= defaults to 100ms.
286
287       DefaultStartLimitIntervalSec=, DefaultStartLimitBurst=
288           Configure the default unit start rate limiting, as configured
289           per-service by StartLimitIntervalSec= and StartLimitBurst=. See
290           systemd.service(5) for details on the per-service settings.
291           DefaultStartLimitIntervalSec= defaults to 10s.
292           DefaultStartLimitBurst= defaults to 5.
293
294       DefaultEnvironment=
295           Configures environment variables passed to all executed processes.
296           Takes a space-separated list of variable assignments. See
297           environ(7) for details about environment variables.
298
299           Simple "%"-specifier expansion is supported, see below for a list
300           of supported specifiers.
301
302           Example:
303
304               DefaultEnvironment="VAR1=word1 word2" VAR2=word3 "VAR3=word 5 6"
305
306           Sets three variables "VAR1", "VAR2", "VAR3".
307
308       ManagerEnvironment=
309           Takes the same arguments as DefaultEnvironment=, see above. Sets
310           environment variables just for the manager process itself. In
311           contrast to user managers, these variables are not inherited by
312           processes spawned by the system manager, use DefaultEnvironment=
313           for that. Note that these variables are merged into the existing
314           environment block. In particular, in case of the system manager,
315           this includes variables set by the kernel based on the kernel
316           command line.
317
318           Setting environment variables for the manager process may be useful
319           to modify its behaviour. See ENVIRONMENT[2] for a descriptions of
320           some variables understood by systemd.
321
322           Simple "%"-specifier expansion is supported, see below for a list
323           of supported specifiers.
324
325       DefaultCPUAccounting=, DefaultBlockIOAccounting=,
326       DefaultMemoryAccounting=, DefaultTasksAccounting=,
327       DefaultIOAccounting=, DefaultIPAccounting=
328           Configure the default resource accounting settings, as configured
329           per-unit by CPUAccounting=, BlockIOAccounting=, MemoryAccounting=,
330           TasksAccounting=, IOAccounting= and IPAccounting=. See
331           systemd.resource-control(5) for details on the per-unit settings.
332           DefaultTasksAccounting= defaults to yes, DefaultMemoryAccounting=
333           to yes.  DefaultCPUAccounting= defaults to yes if enabling CPU
334           accounting doesn't require the CPU controller to be enabled (Linux
335           4.15+ using the unified hierarchy for resource control), otherwise
336           it defaults to no. The other three settings default to no.
337
338       DefaultTasksMax=
339           Configure the default value for the per-unit TasksMax= setting. See
340           systemd.resource-control(5) for details. This setting applies to
341           all unit types that support resource control settings, with the
342           exception of slice units. Defaults to 15% of the minimum of
343           kernel.pid_max=, kernel.threads-max= and root cgroup pids.max.
344           Kernel has a default value for kernel.pid_max= and an algorithm of
345           counting in case of more than 32 cores. For example with the
346           default kernel.pid_max=, DefaultTasksMax= defaults to 4915, but
347           might be greater in other systems or smaller in OS containers.
348
349       DefaultLimitCPU=, DefaultLimitFSIZE=, DefaultLimitDATA=,
350       DefaultLimitSTACK=, DefaultLimitCORE=, DefaultLimitRSS=,
351       DefaultLimitNOFILE=, DefaultLimitAS=, DefaultLimitNPROC=,
352       DefaultLimitMEMLOCK=, DefaultLimitLOCKS=, DefaultLimitSIGPENDING=,
353       DefaultLimitMSGQUEUE=, DefaultLimitNICE=, DefaultLimitRTPRIO=,
354       DefaultLimitRTTIME=
355           These settings control various default resource limits for
356           processes executed by units. See setrlimit(2) for details. These
357           settings may be overridden in individual units using the
358           corresponding LimitXXX= directives and they accept the same
359           parameter syntax, see systemd.exec(5) for details. Note that these
360           resource limits are only defaults for units, they are not applied
361           to the service manager process (i.e. PID 1) itself.
362
363           Most of these settings are unset, which means the resource limits
364           are inherited from the kernel or, if invoked in a container, from
365           the container manager. However, the following have defaults:
366
367DefaultLimitNOFILE= defaults to 1024:524288.
368
369DefaultLimitMEMLOCK= defaults to 8M.
370
371DefaultLimitCORE= does not have a default but it is worth
372               mentioning that RLIMIT_CORE is set to "infinity" by PID 1 which
373               is inherited by its children.
374
375           Note that the service manager internally in PID 1 bumps
376           RLIMIT_NOFILE and RLIMIT_MEMLOCK to higher values, however the
377           limit is reverted to the mentioned defaults for all child processes
378           forked off.
379
380       DefaultOOMPolicy=
381           Configure the default policy for reacting to processes being killed
382           by the Linux Out-Of-Memory (OOM) killer or systemd-oomd. This may
383           be used to pick a global default for the per-unit OOMPolicy=
384           setting. See systemd.service(5) for details. Note that this default
385           is not used for services that have Delegate= turned on.
386
387       DefaultOOMScoreAdjust=
388           Configures the default OOM score adjustments of processes run by
389           the service manager. This defaults to unset (meaning the forked off
390           processes inherit the service manager's OOM score adjustment
391           value), except if the service manager is run for an unprivileged
392           user, in which case this defaults to the service manager's OOM
393           adjustment value plus 100 (this makes service processes slightly
394           more likely to be killed under memory pressure than the manager
395           itself). This may be used to pick a global default for the per-unit
396           OOMScoreAdjust= setting. See systemd.exec(5) for details. Note that
397           this setting has no effect on the OOM score adjustment value of the
398           service manager process itself, it retains the original value set
399           during its invocation.
400

SPECIFIERS

402       Specifiers may be used in the DefaultEnvironment= and
403       ManagerEnvironment= settings. The following expansions are understood:
404
405       Table 1. Specifiers available
406       ┌──────────┬─────────────────────┬────────────────────────┐
407Specifier Meaning             Details                
408       ├──────────┼─────────────────────┼────────────────────────┤
409       │"%a"      │ Architecture        │ A short string         │
410       │          │                     │ identifying the        │
411       │          │                     │ architecture of the    │
412       │          │                     │ local system. A        │
413       │          │                     │ string such as x86,    │
414       │          │                     │ x86-64 or arm64.       │
415       │          │                     │ See the                │
416       │          │                     │ architectures          │
417       │          │                     │ defined for            │
418       │          │                     │ ConditionArchitecture=
419       │          │                     │ in systemd.unit(5)
420       │          │                     │ for a full list.       │
421       ├──────────┼─────────────────────┼────────────────────────┤
422       │"%A"      │ Operating system    │ The operating system   │
423       │          │ image version       │ image version          │
424       │          │                     │ identifier of the      │
425       │          │                     │ running system, as     │
426       │          │                     │ read from the          │
427       │          │                     │ IMAGE_VERSION= field   │
428       │          │                     │ of /etc/os-release. If │
429       │          │                     │ not set, resolves to   │
430       │          │                     │ an empty string. See   │
431       │          │                     │ os-release(5) for more │
432       │          │                     │ information.           │
433       ├──────────┼─────────────────────┼────────────────────────┤
434       │"%b"      │ Boot ID             │ The boot ID of the     │
435       │          │                     │ running system,        │
436       │          │                     │ formatted as string.   │
437       │          │                     │ See random(4) for more │
438       │          │                     │ information.           │
439       ├──────────┼─────────────────────┼────────────────────────┤
440       │"%B"      │ Operating system    │ The operating system   │
441       │          │ build ID            │ build identifier of    │
442       │          │                     │ the running system, as │
443       │          │                     │ read from the          │
444       │          │                     │ BUILD_ID= field of     │
445       │          │                     │ /etc/os-release. If    │
446       │          │                     │ not set, resolves to   │
447       │          │                     │ an empty string. See   │
448       │          │                     │ os-release(5) for more │
449       │          │                     │ information.           │
450       ├──────────┼─────────────────────┼────────────────────────┤
451       │"%H"      │ Host name           │ The hostname of the    │
452       │          │                     │ running system.        │
453       ├──────────┼─────────────────────┼────────────────────────┤
454       │"%l"      │ Short host name     │ The hostname of the    │
455       │          │                     │ running system,        │
456       │          │                     │ truncated at the first │
457       │          │                     │ dot to remove any      │
458       │          │                     │ domain component.      │
459       ├──────────┼─────────────────────┼────────────────────────┤
460       │"%m"      │ Machine ID          │ The machine ID of the  │
461       │          │                     │ running system,        │
462       │          │                     │ formatted as string.   │
463       │          │                     │ See machine-id(5) for  │
464       │          │                     │ more information.      │
465       ├──────────┼─────────────────────┼────────────────────────┤
466       │"%M"      │ Operating system    │ The operating system   │
467       │          │ image identifier    │ image identifier of    │
468       │          │                     │ the running system, as │
469       │          │                     │ read from the          │
470       │          │                     │ IMAGE_ID= field of     │
471       │          │                     │ /etc/os-release. If    │
472       │          │                     │ not set, resolves to   │
473       │          │                     │ an empty string. See   │
474       │          │                     │ os-release(5) for more │
475       │          │                     │ information.           │
476       ├──────────┼─────────────────────┼────────────────────────┤
477       │"%o"      │ Operating system ID │ The operating system   │
478       │          │                     │ identifier of the      │
479       │          │                     │ running system, as     │
480       │          │                     │ read from the ID=
481       │          │                     │ field of               │
482       │          │                     │ /etc/os-release. See   │
483       │          │                     │ os-release(5) for more │
484       │          │                     │ information.           │
485       ├──────────┼─────────────────────┼────────────────────────┤
486       │"%v"      │ Kernel release      │ Identical to uname -r  
487       │          │                     │ output.                │
488       ├──────────┼─────────────────────┼────────────────────────┤
489       │"%w"      │ Operating system    │ The operating system   │
490       │          │ version ID          │ version identifier of  │
491       │          │                     │ the running system, as │
492       │          │                     │ read from the          │
493       │          │                     │ VERSION_ID= field of   │
494       │          │                     │ /etc/os-release. If    │
495       │          │                     │ not set, resolves to   │
496       │          │                     │ an empty string. See   │
497       │          │                     │ os-release(5) for more │
498       │          │                     │ information.           │
499       ├──────────┼─────────────────────┼────────────────────────┤
500       │"%W"      │ Operating system    │ The operating system   │
501       │          │ variant ID          │ variant identifier of  │
502       │          │                     │ the running system, as │
503       │          │                     │ read from the          │
504       │          │                     │ VARIANT_ID= field of   │
505       │          │                     │ /etc/os-release. If    │
506       │          │                     │ not set, resolves to   │
507       │          │                     │ an empty string. See   │
508       │          │                     │ os-release(5) for more │
509       │          │                     │ information.           │
510       ├──────────┼─────────────────────┼────────────────────────┤
511       │"%T"      │ Directory for       │ This is either /tmp or │
512       │          │ temporary files     │ the path "$TMPDIR",    │
513       │          │                     │ "$TEMP" or "$TMP" are  │
514       │          │                     │ set to. (Note that the │
515       │          │                     │ directory may be       │
516       │          │                     │ specified without a    │
517       │          │                     │ trailing slash.)       │
518       ├──────────┼─────────────────────┼────────────────────────┤
519       │"%V"      │ Directory for       │ This is either         │
520       │          │ larger and          │ /var/tmp or the path   │
521       │          │ persistent          │ "$TMPDIR", "$TEMP" or  │
522       │          │ temporary files     │ "$TMP" are set to.     │
523       │          │                     │ (Note that the         │
524       │          │                     │ directory may be       │
525       │          │                     │ specified without a    │
526       │          │                     │ trailing slash.)       │
527       ├──────────┼─────────────────────┼────────────────────────┤
528       │"%%"      │ Single percent sign │ Use "%%" in place of   │
529       │          │                     │ "%" to specify a       │
530       │          │                     │ single percent sign.   │
531       └──────────┴─────────────────────┴────────────────────────┘
532

SEE ALSO

534       systemd(1), systemd.directives(7), systemd.exec(5), systemd.service(5),
535       environ(7), capabilities(7)
536

NOTES

538        1. No New Privileges Flag
539           https://www.kernel.org/doc/html/latest/userspace-api/no_new_privs.html
540
541        2. ENVIRONMENT
542           https://systemd.io/ENVIRONMENT
543
544
545
546systemd 251                                             SYSTEMD-SYSTEM.CONF(5)
Impressum