Debian Codegraph @

upstream/debian-unstable/man1/systemd.1

raw
1 '\" t
2 .TH "SYSTEMD" "1" "" "systemd 261~rc3" "systemd"
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, init \- systemd system and service manager
24 .SH "SYNOPSIS"
25 .HP \w'\fB/usr/lib/systemd/systemd\fR\ 'u
26 \fB/usr/lib/systemd/systemd\fR [OPTIONS...]
27 .HP \w'\fBinit\fR\ 'u
28 \fBinit\fR [OPTIONS...]
29 .SH "DESCRIPTION"
30 .PP
31 systemd is a system and service manager for Linux operating systems\&. When run as first process on boot (as PID 1), it acts as init system that brings up and maintains userspace services\&. Separate instances are started for logged\-in users to start their services\&.
32 .PP
33 \fBsystemd\fR
34 is usually not invoked directly by the user, but is installed as the
35 /sbin/init
36 symlink and started during early boot\&. The user manager instances are started automatically through the
37 \[email protected]\fR(5)
38 service\&.
39 .PP
40 When run as a system instance, systemd interprets the configuration file
41 system\&.conf
42 and the files in
43 system\&.conf\&.d
44 directories; when run as a user instance, systemd interprets the configuration file
45 user\&.conf
46 and the files in
47 user\&.conf\&.d
48 directories\&. See
49 \fBsystemd-system.conf\fR(5)
50 for more information\&.
51 .PP
52 \fBsystemd\fR
53 contains native implementations of various tasks that need to be executed as part of the boot process\&. For example, it sets the hostname or configures the loopback network device\&. It also sets up and mounts various API file systems, such as
54 /sys/,
55 /proc/, and
56 /dev/\&.
57 .PP
58 \fBsystemd\fR
59 will also reset the system clock during early boot if it appears to be set incorrectly\&. See "System clock epoch" section below\&.
60 .PP
61 Note that some but not all interfaces provided by systemd are covered by the
62 \m[blue]\fBInterface Portability and Stability Promise\fR\m[]\&\s-2\u[1]\d\s+2\&.
63 .PP
64 The D\-Bus API of
65 \fBsystemd\fR
66 is described in
67 \fBorg.freedesktop.systemd1\fR(5)
68 and
69 \fBorg.freedesktop.LogControl1\fR(5)\&.
70 .PP
71 Systems which invoke systemd in a container or initrd environment should implement the
72 \m[blue]\fBContainer Interface\fR\m[]\&\s-2\u[2]\d\s+2
73 or
74 \m[blue]\fBinitrd Interface\fR\m[]\&\s-2\u[3]\d\s+2
75 specifications, respectively\&.
76 .SH "UNITS"
77 .PP
78 systemd provides a dependency system between various entities called "units" of 11 different types\&. Units encapsulate various objects that are relevant for system boot\-up and maintenance\&. The majority of units are configured in unit configuration files, whose syntax and basic set of options is described in
79 \fBsystemd.unit\fR(5), however some are created automatically from other configuration files, dynamically from system state or programmatically at runtime\&. Units may be in a number of states, described in the following table\&. Note that the various unit types may have a number of additional substates, which are mapped to the generalized unit states described here\&.
80 .sp
81 .it 1 an-trap
82 .nr an-no-space-flag 1
83 .nr an-break-flag 1
84 .br
85 .B Table\ \&1.\ \&Unit ACTIVE states
86 .TS
87 allbox tab(:);
88 lB lB.
89 T{
90 State
91 T}:T{
92 Description
93 T}
94 .T&
95 l l
96 l l
97 l l
98 l l
99 l l
100 l l
101 l l
102 l l.
103 T{
104 \fIactive\fR
105 T}:T{
106 Started, bound, plugged in, \&..., depending on the unit type\&.
107 T}
108 T{
109 \fIinactive\fR
110 T}:T{
111 Stopped, unbound, unplugged, \&..., depending on the unit type\&.
112 T}
113 T{
114 \fIfailed\fR
115 T}:T{
116 Similar to \fBinactive\fR, but the unit failed in some way (process returned error code on exit, crashed, an operation timed out, or after too many restarts)\&.
117 T}
118 T{
119 \fIactivating\fR
120 T}:T{
121 Changing from \fBinactive\fR to \fBactive\fR\&.
122 T}
123 T{
124 \fIdeactivating\fR
125 T}:T{
126 Changing from \fBactive\fR to \fBinactive\fR\&.
127 T}
128 T{
129 \fImaintenance\fR
130 T}:T{
131 Unit is \fBinactive\fR and a maintenance operation is in progress\&.
132 T}
133 T{
134 \fIreloading\fR
135 T}:T{
136 Unit is \fBactive\fR and it is reloading its configuration\&.
137 T}
138 T{
139 \fIrefreshing\fR
140 T}:T{
141 Unit is \fBactive\fR and a new mount is being activated in its namespace\&.
142 T}
143 .TE
144 .sp 1
145 .PP
146 The following unit types are available:
147 .sp
148 .RS 4
149 .ie n \{\
150 \h'-04' 1.\h'+01'\c
151 .\}
152 .el \{\
153 .sp -1
154 .IP " 1." 4.2
155 .\}
156 Service units, which start and control daemons and the processes they consist of\&. For details, see
157 \fBsystemd.service\fR(5)\&.
158 .RE
159 .sp
160 .RS 4
161 .ie n \{\
162 \h'-04' 2.\h'+01'\c
163 .\}
164 .el \{\
165 .sp -1
166 .IP " 2." 4.2
167 .\}
168 Socket units, which encapsulate local IPC or network sockets in the system, useful for socket\-based activation\&. For details about socket units, see
169 \fBsystemd.socket\fR(5), for details on socket\-based activation and other forms of activation, see
170 \fBdaemon\fR(7)\&.
171 .RE
172 .sp
173 .RS 4
174 .ie n \{\
175 \h'-04' 3.\h'+01'\c
176 .\}
177 .el \{\
178 .sp -1
179 .IP " 3." 4.2
180 .\}
181 Target units are useful to group units, or provide well\-known synchronization points during boot\-up, see
182 \fBsystemd.target\fR(5)\&.
183 .RE
184 .sp
185 .RS 4
186 .ie n \{\
187 \h'-04' 4.\h'+01'\c
188 .\}
189 .el \{\
190 .sp -1
191 .IP " 4." 4.2
192 .\}
193 Device units expose kernel devices in systemd and may be used to implement device\-based activation\&. For details, see
194 \fBsystemd.device\fR(5)\&.
195 .RE
196 .sp
197 .RS 4
198 .ie n \{\
199 \h'-04' 5.\h'+01'\c
200 .\}
201 .el \{\
202 .sp -1
203 .IP " 5." 4.2
204 .\}
205 Mount units control mount points in the file system, for details see
206 \fBsystemd.mount\fR(5)\&.
207 .RE
208 .sp
209 .RS 4
210 .ie n \{\
211 \h'-04' 6.\h'+01'\c
212 .\}
213 .el \{\
214 .sp -1
215 .IP " 6." 4.2
216 .\}
217 Automount units provide automount capabilities, for on\-demand mounting of file systems as well as parallelized boot\-up\&. See
218 \fBsystemd.automount\fR(5)\&.
219 .RE
220 .sp
221 .RS 4
222 .ie n \{\
223 \h'-04' 7.\h'+01'\c
224 .\}
225 .el \{\
226 .sp -1
227 .IP " 7." 4.2
228 .\}
229 Timer units are useful for triggering activation of other units based on timers\&. You may find details in
230 \fBsystemd.timer\fR(5)\&.
231 .RE
232 .sp
233 .RS 4
234 .ie n \{\
235 \h'-04' 8.\h'+01'\c
236 .\}
237 .el \{\
238 .sp -1
239 .IP " 8." 4.2
240 .\}
241 Swap units are very similar to mount units and encapsulate memory swap partitions or files of the operating system\&. They are described in
242 \fBsystemd.swap\fR(5)\&.
243 .RE
244 .sp
245 .RS 4
246 .ie n \{\
247 \h'-04' 9.\h'+01'\c
248 .\}
249 .el \{\
250 .sp -1
251 .IP " 9." 4.2
252 .\}
253 Path units may be used to activate other services when file system objects change or are modified\&. See
254 \fBsystemd.path\fR(5)\&.
255 .RE
256 .sp
257 .RS 4
258 .ie n \{\
259 \h'-04'10.\h'+01'\c
260 .\}
261 .el \{\
262 .sp -1
263 .IP "10." 4.2
264 .\}
265 Slice units may be used to group units which manage system processes (such as service and scope units) in a hierarchical tree for resource management purposes\&. See
266 \fBsystemd.slice\fR(5)\&.
267 .RE
268 .sp
269 .RS 4
270 .ie n \{\
271 \h'-04'11.\h'+01'\c
272 .\}
273 .el \{\
274 .sp -1
275 .IP "11." 4.2
276 .\}
277 Scope units are similar to service units, but manage foreign processes instead of starting them as well\&. See
278 \fBsystemd.scope\fR(5)\&.
279 .RE
280 .PP
281 Units are named as their configuration files\&. Some units have special semantics\&. A detailed list is available in
282 \fBsystemd.special\fR(7)\&.
283 .PP
284 systemd knows various kinds of dependencies, including positive and negative requirement dependencies (i\&.e\&.
285 \fIRequires=\fR
286 and
287 \fIConflicts=\fR) as well as ordering dependencies (\fIAfter=\fR
288 and
289 \fIBefore=\fR)\&. NB: ordering and requirement dependencies are orthogonal\&. If only a requirement dependency exists between two units (e\&.g\&.
290 foo\&.service
291 requires
292 bar\&.service), but no ordering dependency (e\&.g\&.
293 foo\&.service
294 after
295 bar\&.service) and both are requested to start, they will be started in parallel\&. It is a common pattern that both requirement and ordering dependencies are placed between two units\&. Also note that the majority of dependencies are implicitly created and maintained by systemd\&. In most cases, it should be unnecessary to declare additional dependencies manually, however it is possible to do this\&.
296 .PP
297 Application programs and units (via dependencies) may request state changes of units\&. In systemd, these requests are encapsulated as \*(Aqjobs\*(Aq and maintained in a job queue\&. Jobs may succeed or can fail, their execution is ordered based on the ordering dependencies of the units they have been scheduled for\&.
298 .PP
299 On boot systemd activates the target unit
300 default\&.target
301 whose job is to activate on\-boot services and other on\-boot units by pulling them in via dependencies\&. Usually, the unit name is just an alias (symlink) for either
302 graphical\&.target
303 (for fully\-featured boots into the UI) or
304 multi\-user\&.target
305 (for limited console\-only boots for use in embedded or server environments, or similar; a subset of graphical\&.target)\&. However, it is at the discretion of the administrator to configure it as an alias to any other target unit\&. See
306 \fBsystemd.special\fR(7)
307 for details about these target units\&.
308 .PP
309 On first boot,
310 \fBsystemd\fR
311 will enable or disable units according to preset policy\&. See
312 \fBsystemd.preset\fR(5)
313 and "First Boot Semantics" in
314 \fBmachine-id\fR(5)\&.
315 .PP
316 systemd only keeps a minimal set of units loaded into memory\&. Specifically, the only units that are kept loaded into memory are those for which at least one of the following conditions is true:
317 .sp
318 .RS 4
319 .ie n \{\
320 \h'-04' 1.\h'+01'\c
321 .\}
322 .el \{\
323 .sp -1
324 .IP " 1." 4.2
325 .\}
326 It is in an active, activating, deactivating or failed state (i\&.e\&. in any unit state except for
327 "inactive")
328 .RE
329 .sp
330 .RS 4
331 .ie n \{\
332 \h'-04' 2.\h'+01'\c
333 .\}
334 .el \{\
335 .sp -1
336 .IP " 2." 4.2
337 .\}
338 It has a job queued for it
339 .RE
340 .sp
341 .RS 4
342 .ie n \{\
343 \h'-04' 3.\h'+01'\c
344 .\}
345 .el \{\
346 .sp -1
347 .IP " 3." 4.2
348 .\}
349 It is a dependency of at least one other unit that is loaded into memory
350 .RE
351 .sp
352 .RS 4
353 .ie n \{\
354 \h'-04' 4.\h'+01'\c
355 .\}
356 .el \{\
357 .sp -1
358 .IP " 4." 4.2
359 .\}
360 It has some form of resource still allocated (e\&.g\&. a service unit that is inactive but for which a process is still lingering that ignored the request to be terminated)
361 .RE
362 .sp
363 .RS 4
364 .ie n \{\
365 \h'-04' 5.\h'+01'\c
366 .\}
367 .el \{\
368 .sp -1
369 .IP " 5." 4.2
370 .\}
371 It has been pinned into memory programmatically by a D\-Bus call
372 .RE
373 .PP
374 systemd will automatically and implicitly load units from disk \(em if they are not loaded yet \(em as soon as operations are requested for them\&. Thus, in many respects, the fact whether a unit is loaded or not is invisible to clients\&. Use
375 \fBsystemctl list\-units \-\-all\fR
376 to comprehensively list all units currently loaded\&. Any unit for which none of the conditions above applies is promptly unloaded\&. Note that when a unit is unloaded from memory its accounting data is flushed out too\&. However, this data is generally not lost, as a journal log record is generated declaring the consumed resources whenever a unit shuts down\&.
377 .PP
378 Processes systemd spawns are placed in individual Linux control groups named after the unit which they belong to in the private systemd hierarchy\&. (see
379 \m[blue]\fBControl Groups v2\fR\m[]\&\s-2\u[4]\d\s+2
380 for more information about control groups, or short "cgroups")\&. systemd uses this to effectively keep track of processes\&. Control group information is maintained in the kernel, and is accessible via the file system hierarchy (beneath
381 /sys/fs/cgroup/), or in tools such as
382 \fBsystemd-cgls\fR(1)
383 or
384 \fBps\fR(1)
385 (\fBps xawf \-eo pid,user,cgroup,args\fR
386 is particularly useful to list all processes and the systemd units they belong to\&.)\&.
387 .PP
388 systemd is compatible with various established Unix functionality such as
389 /etc/fstab
390 or the
391 utmp
392 database\&.
393 .PP
394 systemd has a minimal transaction system: if a unit is requested to start up or shut down it will add it and all its dependencies to a temporary transaction\&. Then, it will verify if the transaction is consistent (i\&.e\&. whether the ordering of all units is cycle\-free)\&. If it is not, systemd will try to fix it up, and removes non\-essential jobs from the transaction that might remove the loop\&. Also, systemd tries to suppress non\-essential jobs in the transaction that would stop a running service\&. Finally it is checked whether the jobs of the transaction contradict jobs that have already been queued, and optionally the transaction is aborted then\&. If all worked out and the transaction is consistent and minimized in its impact it is merged with all already outstanding jobs and added to the run queue\&. Effectively this means that before executing a requested operation, systemd will verify that it makes sense, fixing it if possible, and only failing if it really cannot work\&.
395 .PP
396 Note that transactions are generated independently of a unit\*(Aqs state at runtime, hence, for example, if a start job is requested on an already started unit, it will still generate a transaction and wake up any inactive dependencies (and cause propagation of other jobs as per the defined relationships)\&. This is because the enqueued job is at the time of execution compared to the target unit\*(Aqs state and is marked successful and complete when both satisfy\&. However, this job also pulls in other dependencies due to the defined relationships and thus leads to, in our example, start jobs for any of those inactive units getting queued as well\&.
397 .PP
398 Units may be generated dynamically at boot and system manager reload time, for example based on other configuration files or parameters passed on the kernel command line\&. For details, see
399 \fBsystemd.generator\fR(7)\&.
400 .SH "DIRECTORIES"
401 .PP
402 System unit directories
403 .RS 4
404 The systemd system manager reads unit configuration from various directories\&. Packages that want to install unit files shall place them in the directory returned by
405 \fBpkg\-config systemd \-\-variable=systemdsystemunitdir\fR\&. Other directories checked are
406 /usr/local/lib/systemd/system
407 and
408 /usr/lib/systemd/system\&. User configuration always takes precedence\&.
409 \fBpkg\-config systemd \-\-variable=systemdsystemconfdir\fR
410 returns the path of the system configuration directory\&. Packages should alter the content of these directories only with the
411 \fBenable\fR
412 and
413 \fBdisable\fR
414 commands of the
415 \fBsystemctl\fR(1)
416 tool\&. Full list of directories is provided in
417 \fBsystemd.unit\fR(5)\&.
418 .RE
419 .PP
420 User unit directories
421 .RS 4
422 Similar rules apply for the user unit directories\&. However, here the
423 \m[blue]\fBXDG Base Directory specification\fR\m[]\&\s-2\u[5]\d\s+2
424 is followed to find units\&. Applications should place their unit files in the directory returned by
425 \fBpkg\-config systemd \-\-variable=systemduserunitdir\fR\&. Global configuration is done in the directory reported by
426 \fBpkg\-config systemd \-\-variable=systemduserconfdir\fR\&. The
427 \fBenable\fR
428 and
429 \fBdisable\fR
430 commands of the
431 \fBsystemctl\fR(1)
432 tool can handle both global (i\&.e\&. for all users) and private (for one user) enabling/disabling of units\&. Full list of directories is provided in
433 \fBsystemd.unit\fR(5)\&.
434 .RE
435 .SH "SIGNALS"
436 .PP
437 The service listens to various UNIX process signals that can be used to request various actions asynchronously\&. The signal handling is enabled very early during boot, before any further processes are invoked\&. However, a supervising container manager or similar that intends to request these operations via this mechanism must take into consideration that this functionality is not available during the earliest initialization phase\&. An
438 \fBsd_notify()\fR
439 notification message carrying the
440 \fIX_SYSTEMD_SIGNALS_LEVEL=2\fR
441 field is emitted once the signal handlers are enabled, see below\&. This may be used to schedule submission of these signals correctly\&.
442 .PP
443 \fBSIGTERM\fR
444 .RS 4
445 Upon receiving this signal the systemd system manager serializes its state, reexecutes itself and deserializes the saved state again\&. This is mostly equivalent to
446 \fBsystemctl daemon\-reexec\fR\&.
447 .sp
448 systemd user managers will start the
449 exit\&.target
450 unit when this signal is received\&. This is mostly equivalent to
451 \fBsystemctl \-\-user start exit\&.target \-\-job\-mode=replace\-irreversibly\fR\&.
452 .RE
453 .PP
454 \fBSIGINT\fR
455 .RS 4
456 Upon receiving this signal the systemd system manager will start the
457 ctrl\-alt\-del\&.target
458 unit\&. This is mostly equivalent to
459 \fBsystemctl start ctrl\-alt\-del\&.target \-\-job\-mode=replace\-irreversibly\fR\&. If this signal is received more than 7 times per 2s, an immediate reboot is triggered\&. Note that pressing
460 Ctrl+Alt+Del
461 on the console will trigger this signal\&. Hence, if a reboot is hanging, pressing
462 Ctrl+Alt+Del
463 more than 7 times in 2 seconds is a relatively safe way to trigger an immediate reboot\&.
464 .sp
465 systemd user managers treat this signal the same way as
466 \fBSIGTERM\fR\&.
467 .RE
468 .PP
469 \fBSIGWINCH\fR
470 .RS 4
471 When this signal is received the systemd system manager will start the
472 kbrequest\&.target
473 unit\&. This is mostly equivalent to
474 \fBsystemctl start kbrequest\&.target\fR\&.
475 .sp
476 This signal is ignored by systemd user managers\&.
477 .RE
478 .PP
479 \fBSIGPWR\fR
480 .RS 4
481 When this signal is received the systemd manager will start the
482 sigpwr\&.target
483 unit\&. This is mostly equivalent to
484 \fBsystemctl start sigpwr\&.target\fR\&.
485 .RE
486 .PP
487 \fBSIGUSR1\fR
488 .RS 4
489 When this signal is received the systemd manager will try to reconnect to the D\-Bus bus\&.
490 .RE
491 .PP
492 \fBSIGUSR2\fR
493 .RS 4
494 When this signal is received the systemd manager will log its complete state in human\-readable form\&. The data logged is the same as printed by
495 \fBsystemd\-analyze dump\fR\&.
496 .RE
497 .PP
498 \fBSIGHUP\fR
499 .RS 4
500 Reloads the complete daemon configuration\&. This is mostly equivalent to
501 \fBsystemctl daemon\-reload\fR\&.
502 .RE
503 .PP
504 \fBSIGRTMIN+0\fR
505 .RS 4
506 Enters default mode, starts the
507 default\&.target
508 unit\&. This is mostly equivalent to
509 \fBsystemctl isolate default\&.target\fR\&.
510 .RE
511 .PP
512 \fBSIGRTMIN+1\fR
513 .RS 4
514 Enters rescue mode, starts the
515 rescue\&.target
516 unit\&. This is mostly equivalent to
517 \fBsystemctl isolate rescue\&.target\fR\&.
518 .RE
519 .PP
520 \fBSIGRTMIN+2\fR
521 .RS 4
522 Enters emergency mode, starts the
523 emergency\&.service
524 unit\&. This is mostly equivalent to
525 \fBsystemctl isolate emergency\&.service\fR\&.
526 .RE
527 .PP
528 \fBSIGRTMIN+3\fR
529 .RS 4
530 Halts the machine, starts the
531 halt\&.target
532 unit\&. This is mostly equivalent to
533 \fBsystemctl start halt\&.target \-\-job\-mode=replace\-irreversibly\fR\&.
534 .RE
535 .PP
536 \fBSIGRTMIN+4\fR
537 .RS 4
538 Powers off the machine, starts the
539 poweroff\&.target
540 unit\&. This is mostly equivalent to
541 \fBsystemctl start poweroff\&.target \-\-job\-mode=replace\-irreversibly\fR\&.
542 .RE
543 .PP
544 \fBSIGRTMIN+5\fR
545 .RS 4
546 Reboots the machine, starts the
547 reboot\&.target
548 unit\&. This is mostly equivalent to
549 \fBsystemctl start reboot\&.target \-\-job\-mode=replace\-irreversibly\fR\&.
550 .RE
551 .PP
552 \fBSIGRTMIN+6\fR
553 .RS 4
554 Reboots the machine via kexec, starts the
555 kexec\&.target
556 unit\&. This is mostly equivalent to
557 \fBsystemctl start kexec\&.target \-\-job\-mode=replace\-irreversibly\fR\&.
558 .RE
559 .PP
560 \fBSIGRTMIN+7\fR
561 .RS 4
562 Reboots userspace, starts the
563 soft\-reboot\&.target
564 unit\&. This is mostly equivalent to
565 \fBsystemctl start soft\-reboot\&.target \-\-job\-mode=replace\-irreversibly\fR\&.
566 .sp
567 Added in version 254\&.
568 .RE
569 .PP
570 \fBSIGRTMIN+13\fR
571 .RS 4
572 Immediately halts the machine\&.
573 .RE
574 .PP
575 \fBSIGRTMIN+14\fR
576 .RS 4
577 Immediately powers off the machine\&.
578 .RE
579 .PP
580 \fBSIGRTMIN+15\fR
581 .RS 4
582 Immediately reboots the machine\&.
583 .RE
584 .PP
585 \fBSIGRTMIN+16\fR
586 .RS 4
587 Immediately reboots the machine with kexec\&.
588 .RE
589 .PP
590 \fBSIGRTMIN+17\fR
591 .RS 4
592 Immediately reboots the userspace\&.
593 .sp
594 Added in version 254\&.
595 .RE
596 .PP
597 \fBSIGRTMIN+20\fR
598 .RS 4
599 Enables display of status messages on the console, as controlled via
600 \fIsystemd\&.show_status=1\fR
601 on the kernel command line\&.
602 .sp
603 You may want to use
604 \fBSetShowStatus()\fR
605 instead of
606 \fBSIGRTMIN+20\fR
607 in order to prevent race conditions\&. See
608 \fBorg.freedesktop.systemd1\fR(5)\&.
609 .RE
610 .PP
611 \fBSIGRTMIN+21\fR
612 .RS 4
613 Disables display of status messages on the console, as controlled via
614 \fIsystemd\&.show_status=0\fR
615 on the kernel command line\&.
616 .sp
617 You may want to use
618 \fBSetShowStatus()\fR
619 instead of
620 \fBSIGRTMIN+21\fR
621 in order to prevent race conditions\&. See
622 \fBorg.freedesktop.systemd1\fR(5)\&.
623 .RE
624 .PP
625 \fBSIGRTMIN+22\fR
626 .RS 4
627 Sets the service manager\*(Aqs log level to
628 "debug", in a fashion equivalent to
629 \fIsystemd\&.log_level=debug\fR
630 on the kernel command line\&.
631 .RE
632 .PP
633 \fBSIGRTMIN+23\fR
634 .RS 4
635 Restores the log level to its configured value\&. The configured value is derived from \(en in order of priority \(en the value specified with
636 \fIsystemd\&.log\-level=\fR
637 on the kernel command line, or the value specified with
638 \fBLogLevel=\fR
639 in the configuration file, or the built\-in default of
640 "info"\&.
641 .sp
642 Added in version 239\&.
643 .RE
644 .PP
645 \fBSIGRTMIN+24\fR
646 .RS 4
647 Immediately exits the manager (only available for \-\-user instances)\&.
648 .sp
649 Added in version 195\&.
650 .RE
651 .PP
652 \fBSIGRTMIN+25\fR
653 .RS 4
654 Upon receiving this signal the systemd manager will reexecute itself\&. This is mostly equivalent to
655 \fBsystemctl daemon\-reexec\fR
656 except that it will be done asynchronously\&.
657 .sp
658 The systemd system manager treats this signal the same way as
659 \fBSIGTERM\fR\&.
660 .sp
661 Added in version 250\&.
662 .RE
663 .PP
664 \fBSIGRTMIN+26\fR
665 .RS 4
666 Restores the log target to its configured value\&. The configured value is derived from \(en in order of priority \(en the value specified with
667 \fIsystemd\&.log\-target=\fR
668 on the kernel command line, or the value specified with
669 \fBLogTarget=\fR
670 in the configuration file, or the built\-in default\&.
671 .sp
672 Added in version 239\&.
673 .RE
674 .PP
675 \fBSIGRTMIN+27\fR, \fBSIGRTMIN+28\fR
676 .RS 4
677 Sets the log target to
678 "console"
679 on
680 \fBSIGRTMIN+27\fR
681 (or
682 "kmsg"
683 on
684 \fBSIGRTMIN+28\fR), in a fashion equivalent to
685 \fIsystemd\&.log_target=console\fR
686 (or
687 \fIsystemd\&.log_target=kmsg\fR
688 on
689 \fBSIGRTMIN+28\fR) on the kernel command line\&.
690 .sp
691 Added in version 239\&.
692 .RE
693 .SH "ENVIRONMENT"
694 .PP
695 The environment block for the system manager is initially set by the kernel\&. (In particular,
696 "key=value"
697 assignments on the kernel command line are turned into environment variables for PID 1)\&. For the user manager, the system manager sets the environment as described in the "Environment Variables in Spawned Processes" section of
698 \fBsystemd.exec\fR(5)\&. The
699 \fIDefaultEnvironment=\fR
700 setting in the system manager applies to all services including
701 user@\&.service\&. Additional entries may be configured (as for any other service) through the
702 \fIEnvironment=\fR
703 and
704 \fIEnvironmentFile=\fR
705 settings for
706 user@\&.service
707 (see
708 \fBsystemd.exec\fR(5))\&. Also, additional environment variables may be set through the
709 \fIManagerEnvironment=\fR
710 setting in
711 \fBsystemd-system.conf\fR(5)
712 and
713 \fBsystemd-user.conf\fR(5)\&.
714 .PP
715 Some of the variables understood by
716 \fBsystemd\fR:
717 .PP
718 \fI$SYSTEMD_LOG_LEVEL\fR
719 .RS 4
720 The maximum log level of emitted messages (messages with a higher log level, i\&.e\&. less important ones, will be suppressed)\&. Takes a comma\-separated list of values\&. A value may be either one of (in order of decreasing importance)
721 \fBemerg\fR,
722 \fBalert\fR,
723 \fBcrit\fR,
724 \fBerr\fR,
725 \fBwarning\fR,
726 \fBnotice\fR,
727 \fBinfo\fR,
728 \fBdebug\fR, or an integer in the range 0\&...7\&. See
729 \fBsyslog\fR(3)
730 for more information\&. Each value may optionally be prefixed with one of
731 \fBconsole\fR,
732 \fBsyslog\fR,
733 \fBkmsg\fR
734 or
735 \fBjournal\fR
736 followed by a colon to set the maximum log level for that specific log target (e\&.g\&.
737 \fBSYSTEMD_LOG_LEVEL=debug,console:info\fR
738 specifies to log at debug level except when logging to the console which should be at info level)\&. Note that the global maximum log level takes priority over any per target maximum log levels\&.
739 .sp
740 This can be overridden with
741 \fB\-\-log\-level=\fR\&.
742 .RE
743 .PP
744 \fI$SYSTEMD_LOG_COLOR\fR
745 .RS 4
746 A boolean\&. If true, messages written to the tty will be colored according to priority\&.
747 .sp
748 This can be overridden with
749 \fB\-\-log\-color=\fR\&.
750 .RE
751 .PP
752 \fI$SYSTEMD_LOG_TIME\fR
753 .RS 4
754 A boolean\&. If true, console log messages will be prefixed with a timestamp\&.
755 .sp
756 This can be overridden with
757 \fB\-\-log\-time=\fR\&.
758 .sp
759 Added in version 246\&.
760 .RE
761 .PP
762 \fI$SYSTEMD_LOG_LOCATION\fR
763 .RS 4
764 A boolean\&. If true, messages will be prefixed with a filename and line number in the source code where the message originates\&.
765 .sp
766 This can be overridden with
767 \fB\-\-log\-location=\fR\&.
768 .RE
769 .PP
770 \fI$SYSTEMD_LOG_TID\fR
771 .RS 4
772 A boolean\&. If true, messages will be prefixed with the current numerical thread ID (TID)\&.
773 .sp
774 Added in version 247\&.
775 .RE
776 .PP
777 \fI$SYSTEMD_LOG_TARGET\fR
778 .RS 4
779 The destination for log messages\&. One of
780 \fBconsole\fR
781 (log to the attached tty),
782 \fBconsole\-prefixed\fR
783 (log to the attached tty but with prefixes encoding the log level and "facility", see
784 \fBsyslog\fR(3),
785 \fBkmsg\fR
786 (log to the kernel circular log buffer),
787 \fBjournal\fR
788 (log to the journal),
789 \fBjournal\-or\-kmsg\fR
790 (log to the journal if available, and to kmsg otherwise),
791 \fBauto\fR
792 (determine the appropriate log target automatically, the default),
793 \fBnull\fR
794 (disable log output)\&.
795 .sp
796 This can be overridden with
797 \fB\-\-log\-target=\fR\&.
798 .RE
799 .PP
800 \fI$SYSTEMD_LOG_RATELIMIT_KMSG\fR
801 .RS 4
802 Whether to ratelimit kmsg or not\&. Takes a boolean\&. Defaults to
803 "true"\&. If disabled, systemd will not ratelimit messages written to kmsg\&.
804 .sp
805 Added in version 254\&.
806 .RE
807 .PP
808 \fI$XDG_CONFIG_HOME\fR, \fI$XDG_CONFIG_DIRS\fR, \fI$XDG_DATA_HOME\fR, \fI$XDG_DATA_DIRS\fR
809 .RS 4
810 The systemd user manager uses these variables in accordance to the
811 \m[blue]\fBXDG Base Directory specification\fR\m[]\&\s-2\u[5]\d\s+2
812 to find its configuration\&.
813 .RE
814 .PP
815 \fI$SYSTEMD_UNIT_PATH\fR, \fI$SYSTEMD_GENERATOR_PATH\fR, \fI$SYSTEMD_ENVIRONMENT_GENERATOR_PATH\fR
816 .RS 4
817 Controls where systemd looks for unit files and generators\&.
818 .sp
819 These variables may contain a list of paths, separated by colons (":")\&. When set, if the list ends with an empty component ("\&.\&.\&.:"), this list is prepended to the usual set of paths\&. Otherwise, the specified list replaces the usual set of paths\&.
820 .RE
821 .PP
822 \fI$SYSTEMD_PAGER\fR, \fI$PAGER\fR
823 .RS 4
824 Pager to use when
825 \fB\-\-no\-pager\fR
826 is not given\&.
827 \fI$SYSTEMD_PAGER\fR
828 is used if set; otherwise
829 \fI$PAGER\fR
830 is used\&. If neither
831 \fI$SYSTEMD_PAGER\fR
832 nor
833 \fI$PAGER\fR
834 are set, a set of well\-known pager implementations is tried in turn, including
835 \fBless\fR(1)
836 and
837 \fBmore\fR(1), until one is found\&. If no pager implementation is discovered, no pager is invoked\&. Setting those environment variables to an empty string or the value
838 "cat"
839 is equivalent to passing
840 \fB\-\-no\-pager\fR\&.
841 .sp
842 Note: if
843 \fI$SYSTEMD_PAGERSECURE\fR
844 is not set,
845 \fI$SYSTEMD_PAGER\fR
846 and
847 \fI$PAGER\fR
848 can only be used to disable the pager (with
849 "cat"
850 or
851 ""), and are otherwise ignored\&.
852 .RE
853 .PP
854 \fI$SYSTEMD_LESS\fR
855 .RS 4
856 Override the options passed to
857 \fBless\fR
858 (by default
859 "FRSXMK")\&.
860 .sp
861 Users might want to change two options in particular:
862 .PP
863 \fBK\fR
864 .RS 4
865 This option instructs the pager to exit immediately when
866 Ctrl+C
867 is pressed\&. To allow
868 \fBless\fR
869 to handle
870 Ctrl+C
871 itself to switch back to the pager command prompt, unset this option\&.
872 .sp
873 If the value of
874 \fI$SYSTEMD_LESS\fR
875 does not include
876 "K", and the pager that is invoked is
877 \fBless\fR,
878 Ctrl+C
879 will be ignored by the executable, and needs to be handled by the pager\&.
880 .RE
881 .PP
882 \fBX\fR
883 .RS 4
884 This option instructs the pager to not send termcap initialization and deinitialization strings to the terminal\&. It is set by default to allow command output to remain visible in the terminal even after the pager exits\&. Nevertheless, this prevents some pager functionality from working, in particular paged output cannot be scrolled with the mouse\&.
885 .RE
886 .sp
887 Note that setting the regular
888 \fI$LESS\fR
889 environment variable has no effect for
890 \fBless\fR
891 invocations by systemd tools\&.
892 .sp
893 See
894 \fBless\fR(1)
895 for more discussion\&.
896 .RE
897 .PP
898 \fI$SYSTEMD_LESSCHARSET\fR
899 .RS 4
900 Override the charset passed to
901 \fBless\fR
902 (by default
903 "utf\-8", if the invoking terminal is determined to be UTF\-8 compatible)\&.
904 .sp
905 Note that setting the regular
906 \fI$LESSCHARSET\fR
907 environment variable has no effect for
908 \fBless\fR
909 invocations by systemd tools\&.
910 .RE
911 .PP
912 \fI$SYSTEMD_PAGERSECURE\fR
913 .RS 4
914 Common pager commands like
915 \fBless\fR(1), in addition to "paging", i\&.e\&. scrolling through the output, support opening of or writing to other files and running arbitrary shell commands\&. When commands are invoked with elevated privileges, for example under
916 \fBsudo\fR(8)
917 or
918 \fBpkexec\fR(1), the pager becomes a security boundary\&. Care must be taken that only programs with strictly limited functionality are used as pagers, and unintended interactive features like opening or creation of new files or starting of subprocesses are not allowed\&. "Secure mode" for the pager may be enabled as described below,
919 \fIif the pager supports that\fR
920 (most pagers are not written in a way that takes this into consideration)\&. It is recommended to either explicitly enable "secure mode" or to completely disable the pager using
921 \fB\-\-no\-pager\fR
922 or
923 \fIPAGER=cat\fR
924 when allowing untrusted users to execute commands with elevated privileges\&.
925 .sp
926 This option takes a boolean argument\&. When set to true, the "secure mode" of the pager is enabled\&. In "secure mode",
927 \fBLESSSECURE=1\fR
928 will be set when invoking the pager, which instructs the pager to disable commands that open or create new files or start new subprocesses\&. Currently only
929 \fBless\fR(1)
930 is known to understand this variable and implement "secure mode"\&.
931 .sp
932 When set to false, no limitation is placed on the pager\&. Setting
933 \fISYSTEMD_PAGERSECURE=0\fR
934 or not removing it from the inherited environment may allow the user to invoke arbitrary commands\&.
935 .sp
936 When
937 \fI$SYSTEMD_PAGERSECURE\fR
938 is not set, systemd tools attempt to automatically figure out if "secure mode" should be enabled and whether the pager supports it\&. "Secure mode" is enabled if the effective UID is not the same as the owner of the login session, see
939 \fBgeteuid\fR(2)
940 and
941 \fBsd_pid_get_owner_uid\fR(3), or when running under
942 \fBsudo\fR(8)
943 or similar tools (\fI$SUDO_UID\fR
944 is set
945 \&\s-2\u[6]\d\s+2)\&. In those cases,
946 \fISYSTEMD_PAGERSECURE=1\fR
947 will be set and pagers which are not known to implement "secure mode" will not be used at all\&. Note that this autodetection only covers the most common mechanisms to elevate privileges and is intended as convenience\&. It is recommended to explicitly set
948 \fI$SYSTEMD_PAGERSECURE\fR
949 or disable the pager\&.
950 .sp
951 Note that if the
952 \fI$SYSTEMD_PAGER\fR
953 or
954 \fI$PAGER\fR
955 variables are to be honoured, other than to disable the pager,
956 \fI$SYSTEMD_PAGERSECURE\fR
957 must be set too\&.
958 .RE
959 .PP
960 \fI$SYSTEMD_COLORS\fR
961 .RS 4
962 Takes a boolean argument, or a special value\&. By default (unset),
963 \fBsystemd\fR
964 and related utilities will use colors in their output if possible\&. If
965 \fI$COLORTERM\fR
966 is set to
967 "truecolor"
968 or
969 "24bit", 24\-bit colors will be enabled, 256 colors otherwise, unless
970 \fI$NO_COLOR\fR
971 or
972 \fI$TERM\fR
973 indicates colors are disabled\&.
974 .PP
975 \fBtrue\fR
976 .RS 4
977 Same as unset, except that
978 \fI$NO_COLOR\fR
979 is ignored\&.
980 .RE
981 .PP
982 \fBfalse\fR
983 .RS 4
984 The output will be monochrome\&.
985 .RE
986 .PP
987 "16", "256", "24bit"
988 .RS 4
989 Always use the base 16 ANSI colors, 256 colors, or 24 bit color, respectively\&.
990 .RE
991 .PP
992 "auto\-16", "auto\-256", "auto\-24bit"
993 .RS 4
994 Use the given quantity of colours, subject to
995 \fI$TERM\fR, and what the console is connected to\&.
996 .RE
997 .RE
998 .PP
999 \fI$SYSTEMD_URLIFY\fR
1000 .RS 4
1001 The value must be a boolean\&. Controls whether clickable links should be generated in the output for terminal emulators supporting this\&. This can be specified to override the decision that
1002 \fBsystemd\fR
1003 makes based on
1004 \fI$TERM\fR
1005 and other conditions\&.
1006 .RE
1007 .PP
1008 \fI$LISTEN_PID\fR, \fI$LISTEN_PIDFDID\fR, \fI$LISTEN_FDS\fR, \fI$LISTEN_FDNAMES\fR
1009 .RS 4
1010 Set by systemd for supervised processes during socket\-based activation\&. See
1011 \fBsd_listen_fds\fR(3)
1012 for more information\&.
1013 .RE
1014 .PP
1015 \fI$NOTIFY_SOCKET\fR
1016 .RS 4
1017 Set by service manager for its services for status and readiness notifications\&. Also consumed by service manager for notifying supervising container managers or service managers up the stack about its own progress\&. See
1018 \fBsd_notify\fR(3)
1019 and the relevant section below for more information\&.
1020 .RE
1021 .PP
1022 For further environment variables understood by systemd and its various components, see
1023 \m[blue]\fBKnown Environment Variables\fR\m[]\&\s-2\u[7]\d\s+2\&.
1024 .SH "KERNEL COMMAND LINE"
1025 .PP
1026 When run as the system instance, systemd parses a number of options listed below\&. They can be specified as kernel command line arguments which are parsed from a number of sources depending on the environment in which systemd is executed\&. If run inside a Linux container, these options are parsed from the command line arguments passed to systemd itself, next to any of the command line options listed in the Options section above\&. If run outside of Linux containers, these arguments are parsed from
1027 /proc/cmdline
1028 instead\&.
1029 .PP
1030 The following variables are understood:
1031 .PP
1032 \fIsystemd\&.unit=\fR, \fIrd\&.systemd\&.unit=\fR
1033 .RS 4
1034 Overrides the unit to activate on boot\&. Defaults to
1035 default\&.target\&. This may be used to temporarily boot into a different boot unit, for example
1036 rescue\&.target
1037 or
1038 emergency\&.service\&. See
1039 \fBsystemd.special\fR(7)
1040 for details about these units\&. The option prefixed with
1041 "rd\&."
1042 is honored only in the initrd, while the one that is not prefixed only in the main system\&.
1043 .RE
1044 .PP
1045 \fIsystemd\&.dump_core\fR
1046 .RS 4
1047 Takes a boolean argument or enables the option if specified without an argument\&. If enabled, the systemd manager (PID 1) dumps core when it crashes\&. Otherwise, no core dump is created\&. Defaults to enabled\&.
1048 .sp
1049 Added in version 233\&.
1050 .RE
1051 .PP
1052 \fIsystemd\&.crash_chvt\fR
1053 .RS 4
1054 Takes a positive integer, or a boolean argument\&. Can be also specified without an argument, with the same effect as a positive boolean\&. If a positive integer (in the range 1\(en63) is specified, the system manager (PID 1) will activate the specified virtual terminal when it crashes\&. Defaults to disabled, meaning that no such switch is attempted\&. If set to enabled, the virtual terminal the kernel messages are written to is used instead\&.
1055 .sp
1056 Added in version 233\&.
1057 .RE
1058 .PP
1059 \fIsystemd\&.crash_shell\fR
1060 .RS 4
1061 Takes a boolean argument or enables the option if specified without an argument\&. If enabled, the system manager (PID 1) spawns a shell when it crashes\&. Otherwise, no shell is spawned\&. Defaults to disabled, for security reasons, as the shell is not protected by password authentication\&.
1062 .sp
1063 Added in version 233\&.
1064 .RE
1065 .PP
1066 \fIsystemd\&.crash_action=\fR
1067 .RS 4
1068 Takes one of
1069 "freeze",
1070 "reboot"
1071 or
1072 "poweroff"\&. Defaults to
1073 "freeze"\&. If set to
1074 "freeze", the system will hang indefinitely when the system manager (PID 1) crashes\&. If set to
1075 "reboot", the system manager (PID 1) will reboot the machine automatically when it crashes, after a 10s delay\&. If set to
1076 "poweroff", the system manager (PID 1) will power off the machine immediately when it crashes\&. If combined with
1077 \fIsystemd\&.crash_shell\fR, the configured crash action is executed after the shell exits\&.
1078 .sp
1079 Added in version 256\&.
1080 .RE
1081 .PP
1082 \fIsystemd\&.confirm_spawn\fR
1083 .RS 4
1084 Takes a boolean argument or a path to the virtual console where the confirmation messages should be emitted\&. Can be also specified without an argument, with the same effect as a positive boolean\&. If enabled, the system manager (PID 1) asks for confirmation when spawning processes using
1085 \fB/dev/console\fR\&. If a path or a console name (such as
1086 "ttyS0") is provided, the virtual console pointed to by this path or described by the give name will be used instead\&. Defaults to disabled\&.
1087 .sp
1088 Added in version 233\&.
1089 .RE
1090 .PP
1091 \fIsystemd\&.service_watchdogs=\fR
1092 .RS 4
1093 Takes a boolean argument\&. If disabled, all service runtime watchdogs (\fBWatchdogSec=\fR) and emergency actions (e\&.g\&.
1094 \fBOnFailure=\fR
1095 or
1096 \fBStartLimitAction=\fR) are ignored by the system manager (PID 1); see
1097 \fBsystemd.service\fR(5)\&. Defaults to enabled, i\&.e\&. watchdogs and failure actions are processed normally\&. The hardware watchdog is not affected by this option\&.
1098 .sp
1099 Added in version 237\&.
1100 .RE
1101 .PP
1102 \fIsystemd\&.show_status\fR
1103 .RS 4
1104 Takes a boolean argument or the constants
1105 \fBerror\fR
1106 and
1107 \fBauto\fR\&. Can be also specified without an argument, with the same effect as a positive boolean\&. If enabled, the systemd manager (PID 1) shows terse service status updates on the console during bootup\&. With
1108 \fBerror\fR, only messages about failures are shown, but boot is otherwise quiet\&.
1109 \fBauto\fR
1110 behaves like
1111 \fBfalse\fR
1112 until there is a significant delay in boot\&. Defaults to enabled, unless
1113 \fBquiet\fR
1114 is passed as kernel command line option, in which case it defaults to
1115 \fBerror\fR\&. If specified overrides the system manager configuration file option
1116 \fBShowStatus=\fR, see
1117 \fBsystemd-system.conf\fR(5)\&.
1118 .sp
1119 Added in version 233\&.
1120 .RE
1121 .PP
1122 \fIsystemd\&.status_unit_format=\fR
1123 .RS 4
1124 Takes
1125 \fBname\fR,
1126 \fBdescription\fR
1127 or
1128 \fBcombined\fR
1129 as the value\&. If
1130 \fBname\fR, the system manager will use unit names in status messages\&. If
1131 \fBcombined\fR, the system manager will use unit names and description in status messages\&. When specified, overrides the system manager configuration file option
1132 \fBStatusUnitFormat=\fR, see
1133 \fBsystemd-system.conf\fR(5)\&.
1134 .sp
1135 Added in version 243\&.
1136 .RE
1137 .PP
1138 \fIsystemd\&.log_color\fR, \fIsystemd\&.log_level=\fR, \fIsystemd\&.log_location\fR, \fIsystemd\&.log_target=\fR, \fIsystemd\&.log_time\fR, \fIsystemd\&.log_tid\fR, \fIsystemd\&.log_ratelimit_kmsg\fR
1139 .RS 4
1140 Controls log output, with the same effect as the
1141 \fI$SYSTEMD_LOG_COLOR\fR,
1142 \fI$SYSTEMD_LOG_LEVEL\fR,
1143 \fI$SYSTEMD_LOG_LOCATION\fR,
1144 \fI$SYSTEMD_LOG_TARGET\fR,
1145 \fI$SYSTEMD_LOG_TIME\fR,
1146 \fI$SYSTEMD_LOG_TID\fR
1147 and
1148 \fI$SYSTEMD_LOG_RATELIMIT_KMSG\fR
1149 environment variables described above\&.
1150 \fIsystemd\&.log_color\fR,
1151 \fIsystemd\&.log_location\fR,
1152 \fIsystemd\&.log_time\fR,
1153 \fIsystemd\&.log_tid\fR
1154 and
1155 \fIsystemd\&.log_ratelimit_kmsg\fR
1156 can be specified without an argument, with the same effect as a positive boolean\&.
1157 .RE
1158 .PP
1159 \fIsystemd\&.default_standard_output=\fR, \fIsystemd\&.default_standard_error=\fR
1160 .RS 4
1161 Controls default standard output and error output for services and sockets\&. That is, controls the default for
1162 \fBStandardOutput=\fR
1163 and
1164 \fBStandardError=\fR
1165 (see
1166 \fBsystemd.exec\fR(5)
1167 for details)\&. Takes one of
1168 \fBinherit\fR,
1169 \fBnull\fR,
1170 \fBtty\fR,
1171 \fBjournal\fR,
1172 \fBjournal+console\fR,
1173 \fBkmsg\fR,
1174 \fBkmsg+console\fR\&. If the argument is omitted
1175 \fIsystemd\&.default\-standard\-output=\fR
1176 defaults to
1177 \fBjournal\fR
1178 and
1179 \fIsystemd\&.default\-standard\-error=\fR
1180 to
1181 \fBinherit\fR\&.
1182 .RE
1183 .PP
1184 \fIsystemd\&.setenv=\fR
1185 .RS 4
1186 Takes a string argument in the form VARIABLE=VALUE\&. May be used to set default environment variables to add to forked child processes\&. May be used more than once to set multiple variables\&.
1187 .RE
1188 .PP
1189 \fIsystemd\&.machine_id=\fR
1190 .RS 4
1191 Takes a 32 character hex value to be used for setting the machine\-id\&. Intended mostly for network booting where the same machine\-id is desired for every boot\&.
1192 .sp
1193 Added in version 229\&.
1194 .RE
1195 .PP
1196 \fIsystemd\&.set_credential=\fR, \fIsystemd\&.set_credential_binary=\fR
1197 .RS 4
1198 Sets a system credential, which can then be propagated to system services using the
1199 \fIImportCredential=\fR
1200 or
1201 \fILoadCredential=\fR
1202 setting, see
1203 \fBsystemd.exec\fR(5)
1204 for details\&. Takes a pair of credential name and value, separated by a colon\&. The
1205 \fIsystemd\&.set_credential=\fR
1206 parameter expects the credential value in literal text form, the
1207 \fIsystemd\&.set_credential_binary=\fR
1208 parameter takes binary data encoded in Base64\&. Note that the kernel command line is typically accessible by unprivileged programs in
1209 /proc/cmdline\&. Thus, this mechanism is not suitable for transferring sensitive data\&. Use it only for data that is not sensitive (e\&.g\&. public keys/certificates, rather than private keys), or in testing/debugging environments\&.
1210 .sp
1211 For further information see
1212 \m[blue]\fBSystem and Service Credentials\fR\m[]\&\s-2\u[8]\d\s+2
1213 documentation\&.
1214 .sp
1215 Added in version 251\&.
1216 .RE
1217 .PP
1218 \fIsystemd\&.import_credentials=\fR
1219 .RS 4
1220 Takes a boolean argument\&. If false disables importing credentials from the kernel command line, the DMI/SMBIOS OEM string table, the qemu_fw_cfg subsystem or the EFI kernel stub\&.
1221 .sp
1222 Added in version 251\&.
1223 .RE
1224 .PP
1225 \fIquiet\fR
1226 .RS 4
1227 Turn off status output at boot, much like
1228 \fIsystemd\&.show_status=no\fR
1229 would\&. Note that this option is also read by the kernel itself and disables kernel log output\&. Passing this option hence turns off the usual output from both the system manager and the kernel\&.
1230 .sp
1231 Added in version 186\&.
1232 .RE
1233 .PP
1234 \fIdebug\fR
1235 .RS 4
1236 Turn on debugging output\&. This is equivalent to
1237 \fIsystemd\&.log_level=debug\fR\&. Note that this option is also read by the kernel itself and enables kernel debug output\&. Passing this option hence turns on the debug output from both the system manager and the kernel\&.
1238 .sp
1239 Added in version 205\&.
1240 .RE
1241 .PP
1242 \fIemergency\fR, \fIrd\&.emergency\fR
1243 .RS 4
1244 Boot into emergency mode\&. Those options are equivalent to
1245 \fIsystemd\&.unit=emergency\&.target\fR
1246 or
1247 \fIrd\&.systemd\&.unit=emergency\&.target\fR, respectively\&. They were initially provided for compatibility with SysV, but are retained as convenient shortcuts\&.
1248 .sp
1249 Added in version 186\&.
1250 .RE
1251 .PP
1252 \fIrescue\fR, \fIrd\&.rescue\fR, \fIsingle\fR, \fI1\fR
1253 .RS 4
1254 Boot into rescue mode\&. Those options are equivalent to either
1255 \fIsystemd\&.unit=rescue\&.target\fR
1256 or
1257 \fIrd\&.systemd\&.unit=rescue\&.target\fR\&. They were initially provided for compatibility with SysV, but are retained as convenient shortcuts\&.
1258 .sp
1259 Added in version 186\&.
1260 .RE
1261 .PP
1262 \fI3\fR, \fI5\fR
1263 .RS 4
1264 Shortcuts to boot into specific targets:
1265 \fI3\fR
1266 is equivalent to
1267 \fIsystemd\&.unit=multi\-user\&.target\fR
1268 and
1269 \fI5\fR
1270 is equivalent to
1271 \fIsystemd\&.unit=graphical\&.target\fR\&. Those options were initially provided for compatibility with SysV, but are retained as convenient shortcuts\&.
1272 .sp
1273 Added in version 186\&.
1274 .RE
1275 .PP
1276 \fIlocale\&.LANG=\fR, \fIlocale\&.LANGUAGE=\fR, \fIlocale\&.LC_CTYPE=\fR, \fIlocale\&.LC_NUMERIC=\fR, \fIlocale\&.LC_TIME=\fR, \fIlocale\&.LC_COLLATE=\fR, \fIlocale\&.LC_MONETARY=\fR, \fIlocale\&.LC_MESSAGES=\fR, \fIlocale\&.LC_PAPER=\fR, \fIlocale\&.LC_NAME=\fR, \fIlocale\&.LC_ADDRESS=\fR, \fIlocale\&.LC_TELEPHONE=\fR, \fIlocale\&.LC_MEASUREMENT=\fR, \fIlocale\&.LC_IDENTIFICATION=\fR
1277 .RS 4
1278 Set the system locale to use\&. This overrides the settings in
1279 /etc/locale\&.conf\&. For more information, see
1280 \fBlocale.conf\fR(5)
1281 and
1282 \fBlocale\fR(7)\&.
1283 .sp
1284 Added in version 186\&.
1285 .RE
1286 .PP
1287 \fIsystemd\&.minimum_uptime_sec=\fR
1288 .RS 4
1289 Takes a time in seconds\&. Specifies the minimum uptime of the system before the system shuts down\&. For more information see the
1290 \fIMinimumUptimeSec=\fR
1291 setting described in
1292 \fBsystemd-system.conf\fR(5)\&.
1293 .sp
1294 Added in version 261\&.
1295 .RE
1296 .PP
1297 For other kernel command line parameters understood by components of the core OS, please refer to
1298 \fBkernel-command-line\fR(7)\&.
1299 .SH "SYSTEM CREDENTIALS"
1300 .PP
1301 During initialization the service manager will import credentials from various sources into the system\*(Aqs set of credentials, which can then be propagated into services and consumed by generators:
1302 .sp
1303 .RS 4
1304 .ie n \{\
1305 \h'-04'\(bu\h'+03'\c
1306 .\}
1307 .el \{\
1308 .sp -1
1309 .IP \(bu 2.3
1310 .\}
1311 When the service manager first initializes it will read system credentials from SMBIOS Type 11 vendor strings
1312 \fIio\&.systemd\&.credential:\fR\fI\fIname\fR\fR\fI=\fR\fI\fIvalue\fR\fR, and
1313 \fIio\&.systemd\&.credential\&.binary:\fR\fI\fIname\fR\fR\fI=\fR\fI\fIvalue\fR\fR\&.
1314 .RE
1315 .sp
1316 .RS 4
1317 .ie n \{\
1318 \h'-04'\(bu\h'+03'\c
1319 .\}
1320 .el \{\
1321 .sp -1
1322 .IP \(bu 2.3
1323 .\}
1324 At the same time it will import credentials from QEMU
1325 "fw_cfg"\&. (Note that the SMBIOS mechanism is generally preferred, because it is faster and generic\&.)
1326 .RE
1327 .sp
1328 .RS 4
1329 .ie n \{\
1330 \h'-04'\(bu\h'+03'\c
1331 .\}
1332 .el \{\
1333 .sp -1
1334 .IP \(bu 2.3
1335 .\}
1336 Credentials may be passed via the kernel command line, using the
1337 \fIsystemd\&.set\-credential=\fR
1338 parameter, see above\&.
1339 .RE
1340 .sp
1341 .RS 4
1342 .ie n \{\
1343 \h'-04'\(bu\h'+03'\c
1344 .\}
1345 .el \{\
1346 .sp -1
1347 .IP \(bu 2.3
1348 .\}
1349 Credentials may be passed from the UEFI environment via
1350 \fBsystemd-stub\fR(7)\&.
1351 .RE
1352 .sp
1353 .RS 4
1354 .ie n \{\
1355 \h'-04'\(bu\h'+03'\c
1356 .\}
1357 .el \{\
1358 .sp -1
1359 .IP \(bu 2.3
1360 .\}
1361 When the service manager is invoked during the initrd → host transition it will import all files in
1362 /run/credentials/@initrd/
1363 as system credentials\&.
1364 .RE
1365 .PP
1366 Invoke
1367 \fBsystemd-creds\fR(1)
1368 as follows to see the list of credentials passed into the system:
1369 .sp
1370 .if n \{\
1371 .RS 4
1372 .\}
1373 .nf
1374 # systemd\-creds \-\-system list
1375 .fi
1376 .if n \{\
1377 .RE
1378 .\}
1379 .PP
1380 For further information see
1381 \m[blue]\fBSystem and Service Credentials\fR\m[]\&\s-2\u[8]\d\s+2
1382 documentation\&.
1383 .PP
1384 The service manager when run as PID 1 consumes the following system credentials:
1385 .PP
1386 \fIvmm\&.notify_socket\fR
1387 .RS 4
1388 Contains a
1389 \fBAF_VSOCK\fR
1390 or
1391 \fBAF_UNIX\fR
1392 address where to send a
1393 \fBREADY=1\fR
1394 notification message when the service manager has completed booting\&. See
1395 \fBsd_notify\fR(3)
1396 and the next section for more information\&. Note that in case the hypervisor does not support
1397 \fBSOCK_DGRAM\fR
1398 over
1399 \fBAF_VSOCK\fR,
1400 \fBSOCK_SEQPACKET\fR
1401 will be tried instead\&. The credential payload for
1402 \fBAF_VSOCK\fR
1403 should be a string in the form
1404 "vsock:CID:PORT"\&.
1405 "vsock\-stream",
1406 "vsock\-dgram"
1407 and
1408 "vsock\-seqpacket"
1409 can be used instead of
1410 "vsock"
1411 to force usage of the corresponding socket type\&.
1412 .sp
1413 This feature is useful for machine managers or other processes on the host to receive a notification via VSOCK when a virtual machine has finished booting\&.
1414 .sp
1415 Added in version 254\&.
1416 .RE
1417 .PP
1418 \fIsystem\&.machine_id\fR
1419 .RS 4
1420 Takes a 128bit hexadecimal ID to initialize
1421 /etc/machine\-id
1422 from, if the file is not set up yet\&. See
1423 \fBmachine-id\fR(5)
1424 for details\&.
1425 .sp
1426 Added in version 254\&.
1427 .RE
1428 .PP
1429 For a list of system credentials various other components of systemd consume, see
1430 \fBsystemd.system-credentials\fR(7)\&.
1431 .SH "READINESS PROTOCOL"
1432 .PP
1433 The service manager implements a readiness notification protocol both between the manager and its services (i\&.e\&. down the stack), and between the manager and a potential supervisor further up the stack (the latter could be a machine or container manager, or in case of a per\-user service manager the system service manager instance)\&. The basic protocol (and the suggested API for it) is described in
1434 \fBsd_notify\fR(3)\&.
1435 .PP
1436 The notification socket the service manager (including PID 1) uses for reporting readiness to its own supervisor is set via the usual
1437 \fI$NOTIFY_SOCKET\fR
1438 environment variable (see above)\&. Since this is directly settable only for container managers and for the per\-user instance of the service manager, an additional mechanism to configure this is available, in particular intended for use in VM environments: the
1439 \fIvmm\&.notify_socket\fR
1440 system credential (see above) may be set to a suitable socket (typically an
1441 \fBAF_VSOCK\fR
1442 one) via SMBIOS Type 11 vendor strings\&. For details see above\&.
1443 .PP
1444 The notification protocol from the service manager up the stack towards a supervisor supports a number of extension fields that allow a supervisor to learn about specific properties of the system and track its boot progress\&. Specifically the following fields are sent:
1445 .sp
1446 .RS 4
1447 .ie n \{\
1448 \h'-04'\(bu\h'+03'\c
1449 .\}
1450 .el \{\
1451 .sp -1
1452 .IP \(bu 2.3
1453 .\}
1454 An
1455 \fIX_SYSTEMD_HOSTNAME=\&...\fR
1456 message will be sent out once the initial hostname for the system has been determined\&. Note that during later runtime the hostname might be changed again programmatically, and (currently) no further notifications are sent out in that case\&.
1457 .sp
1458 Added in version 256\&.
1459 .RE
1460 .sp
1461 .RS 4
1462 .ie n \{\
1463 \h'-04'\(bu\h'+03'\c
1464 .\}
1465 .el \{\
1466 .sp -1
1467 .IP \(bu 2.3
1468 .\}
1469 An
1470 \fIX_SYSTEMD_MACHINE_ID=\&...\fR
1471 message will be sent out once the machine ID of the system has been determined\&. See
1472 \fBmachine-id\fR(5)
1473 for details\&.
1474 .sp
1475 Added in version 256\&.
1476 .RE
1477 .sp
1478 .RS 4
1479 .ie n \{\
1480 \h'-04'\(bu\h'+03'\c
1481 .\}
1482 .el \{\
1483 .sp -1
1484 .IP \(bu 2.3
1485 .\}
1486 An
1487 \fIX_SYSTEMD_SIGNALS_LEVEL=\&...\fR
1488 message will be sent out once the service manager installed the various UNIX process signal handlers described above\&. The field\*(Aqs value is an unsigned integer formatted as decimal string, and indicates the supported UNIX process signal feature level of the service manager\&. Currently, only a single feature level is defined:
1489 .sp
1490 .RS 4
1491 .ie n \{\
1492 \h'-04'\(bu\h'+03'\c
1493 .\}
1494 .el \{\
1495 .sp -1
1496 .IP \(bu 2.3
1497 .\}
1498 \fIX_SYSTEMD_SIGNALS_LEVEL=2\fR
1499 covers the various UNIX process signals documented above \(en which are a superset of those supported by the historical SysV init system\&.
1500 .RE
1501 .sp
1502 Signals sent to PID 1 before this message is sent might not be handled correctly yet\&. A consumer of these messages should parse the value as an unsigned integer that indicates the level of support\&. For now only the mentioned level 2 is defined, but later on additional levels might be defined with higher integers, that will implement a superset of the currently defined behaviour\&.
1503 .sp
1504 Added in version 256\&.
1505 .RE
1506 .sp
1507 .RS 4
1508 .ie n \{\
1509 \h'-04'\(bu\h'+03'\c
1510 .\}
1511 .el \{\
1512 .sp -1
1513 .IP \(bu 2.3
1514 .\}
1515 \fIX_SYSTEMD_UNIT_ACTIVE=\&...\fR
1516 and
1517 \fIX_SYSTEMD_UNIT_INACTIVE=\&...\fR
1518 messages will be sent out for each target unit as it becomes active or stops being active\&. This is useful to track boot progress and functionality\&. For example, once the
1519 ssh\-access\&.target
1520 unit is reported started SSH access is typically available, see
1521 \fBsystemd.special\fR(7)
1522 for details\&.
1523 .sp
1524 Added in version 256\&.
1525 .RE
1526 .sp
1527 .RS 4
1528 .ie n \{\
1529 \h'-04'\(bu\h'+03'\c
1530 .\}
1531 .el \{\
1532 .sp -1
1533 .IP \(bu 2.3
1534 .\}
1535 An
1536 \fIX_SYSTEMD_SHUTDOWN=\&...\fR
1537 message will be sent out very shortly before the system shuts down\&. The value is one of the strings
1538 "reboot",
1539 "halt",
1540 "poweroff",
1541 "kexec"
1542 and indicates which kind of shutdown is being executed\&.
1543 .sp
1544 Added in version 256\&.
1545 .RE
1546 .sp
1547 .RS 4
1548 .ie n \{\
1549 \h'-04'\(bu\h'+03'\c
1550 .\}
1551 .el \{\
1552 .sp -1
1553 .IP \(bu 2.3
1554 .\}
1555 An
1556 \fIX_SYSTEMD_REBOOT_PARAMETER=\&...\fR
1557 message will also be sent out very shortly before the system shuts down\&. Its value is the reboot argument as configured with
1558 \fBsystemctl \-\-reboot\-argument=\&...\fR\&.
1559 .sp
1560 Added in version 256\&.
1561 .RE
1562 .PP
1563 Note that these extension fields are sent in addition to the regular
1564 "READY=1"
1565 and
1566 "RELOADING=1"
1567 notifications\&.
1568 .SH "OPTIONS"
1569 .PP
1570 \fBsystemd\fR
1571 is only very rarely invoked directly, since it is started early and is already running by the time users may interact with it\&. Normally, tools like
1572 \fBsystemctl\fR(1)
1573 are used to give commands to the manager\&. Since
1574 \fBsystemd\fR
1575 is usually not invoked directly, the options listed below are mostly useful for debugging and special purposes\&.
1576 .SS "Introspection and debugging options"
1577 .PP
1578 Those options are used for testing and introspection, and
1579 \fBsystemd\fR
1580 may be invoked with them at any time:
1581 .PP
1582 \fB\-\-dump\-configuration\-items\fR
1583 .RS 4
1584 Dump understood unit configuration items\&. This outputs a terse but complete list of configuration items understood in unit definition files\&.
1585 .RE
1586 .PP
1587 \fB\-\-dump\-bus\-properties\fR
1588 .RS 4
1589 Dump exposed bus properties\&. This outputs a terse but complete list of properties exposed on D\-Bus\&.
1590 .sp
1591 Added in version 239\&.
1592 .RE
1593 .PP
1594 \fB\-\-test\fR
1595 .RS 4
1596 Determine the initial start\-up transaction (i\&.e\&. the list of jobs enqueued at start\-up), dump it and exit \(em without actually executing any of the determined jobs\&. This option is useful for debugging only\&. Note that during regular service manager start\-up additional units not shown by this operation may be started, because hardware, socket, bus or other kinds of activation might add additional jobs as the transaction is executed\&. Use
1597 \fB\-\-system\fR
1598 to request the initial transaction of the system service manager (this is also the implied default), combine with
1599 \fB\-\-user\fR
1600 to request the initial transaction of the per\-user service manager instead\&.
1601 .RE
1602 .PP
1603 \fB\-\-system\fR, \fB\-\-user\fR
1604 .RS 4
1605 When used in conjunction with
1606 \fB\-\-test\fR, selects whether to calculate the initial transaction for the system instance or for a per\-user instance\&. These options have no effect when invoked without
1607 \fB\-\-test\fR, as during regular (i\&.e\&. non\-\fB\-\-test\fR) invocations the service manager will automatically detect whether it shall operate in system or per\-user mode, by checking whether the PID it is run as is 1 or not\&. Note that it is not supported booting and maintaining a system with the service manager running in
1608 \fB\-\-system\fR
1609 mode but with a PID other than 1\&.
1610 .RE
1611 .PP
1612 \fB\-h\fR, \fB\-\-help\fR
1613 .RS 4
1614 Print a short help text and exit\&.
1615 .RE
1616 .PP
1617 \fB\-\-version\fR
1618 .RS 4
1619 Print a short version string and exit\&.
1620 .RE
1621 .SS "Options that duplicate kernel command line settings"
1622 .PP
1623 Those options correspond directly to options listed above in "Kernel Command Line"\&. Both forms may be used equivalently for the system manager, but it is recommended to use the forms listed above in this context, because they are properly namespaced\&. When an option is specified both on the kernel command line and as a normal command line argument, the latter has higher precedence\&.
1624 .PP
1625 When
1626 \fBsystemd\fR
1627 is used as a user manager, the kernel command line is ignored and only the options described below are understood\&. Nevertheless,
1628 \fBsystemd\fR
1629 is usually started in this mode through the
1630 \[email protected]\fR(5)
1631 service, which is shared between all users\&. It may be more convenient to use configuration files to modify settings (see
1632 \fBsystemd-user.conf\fR(5)), or environment variables\&. See the "Environment" section above for a discussion of how the environment block is set\&.
1633 .PP
1634 \fB\-\-unit=\fR
1635 .RS 4
1636 Set default unit to activate on startup\&. If not specified, defaults to
1637 default\&.target\&. See
1638 \fIsystemd\&.unit=\fR
1639 above\&.
1640 .RE
1641 .PP
1642 \fB\-\-dump\-core\fR
1643 .RS 4
1644 Enable core dumping on crash\&. This switch has no effect when running as user instance\&. Same as
1645 \fIsystemd\&.dump_core=\fR
1646 above\&.
1647 .RE
1648 .PP
1649 \fB\-\-crash\-vt=\fR\fB\fIVT\fR\fR
1650 .RS 4
1651 Switch to a specific virtual console (VT) on crash\&. This switch has no effect when running as user instance\&. Same as
1652 \fIsystemd\&.crash_chvt=\fR
1653 above (but not the different spelling!)\&.
1654 .sp
1655 Added in version 227\&.
1656 .RE
1657 .PP
1658 \fB\-\-crash\-shell\fR
1659 .RS 4
1660 Run a shell on crash\&. This switch has no effect when running as user instance\&. See
1661 \fIsystemd\&.crash_shell=\fR
1662 above\&.
1663 .RE
1664 .PP
1665 \fB\-\-crash\-action=\fR
1666 .RS 4
1667 Specify what to do when the system manager (PID 1) crashes\&. This switch has no effect when
1668 \fBsystemd\fR
1669 is running as user instance\&. See
1670 \fIsystemd\&.crash_action=\fR
1671 above\&.
1672 .sp
1673 Added in version 256\&.
1674 .RE
1675 .PP
1676 \fB\-\-confirm\-spawn\fR
1677 .RS 4
1678 Ask for confirmation when spawning processes\&. This switch has no effect when run as user instance\&. See
1679 \fIsystemd\&.confirm_spawn\fR
1680 above\&.
1681 .RE
1682 .PP
1683 \fB\-\-show\-status\fR
1684 .RS 4
1685 Show terse unit status information on the console during boot\-up and shutdown\&. See
1686 \fIsystemd\&.show_status\fR
1687 above\&.
1688 .sp
1689 Added in version 244\&.
1690 .RE
1691 .PP
1692 \fB\-\-log\-color\fR
1693 .RS 4
1694 Highlight important log messages\&. See
1695 \fIsystemd\&.log_color\fR
1696 above\&.
1697 .sp
1698 Added in version 244\&.
1699 .RE
1700 .PP
1701 \fB\-\-log\-level=\fR
1702 .RS 4
1703 Set log level\&. See
1704 \fIsystemd\&.log_level\fR
1705 above\&.
1706 .RE
1707 .PP
1708 \fB\-\-log\-location\fR
1709 .RS 4
1710 Include code location in log messages\&. See
1711 \fIsystemd\&.log_location\fR
1712 above\&.
1713 .sp
1714 Added in version 244\&.
1715 .RE
1716 .PP
1717 \fB\-\-log\-target=\fR
1718 .RS 4
1719 Set log target\&. See
1720 \fIsystemd\&.log_target\fR
1721 above\&.
1722 .RE
1723 .PP
1724 \fB\-\-log\-time=\fR
1725 .RS 4
1726 Prefix console messages with timestamp\&. See
1727 \fIsystemd\&.log_time\fR
1728 above\&.
1729 .sp
1730 Added in version 246\&.
1731 .RE
1732 .PP
1733 \fB\-\-machine\-id=\fR
1734 .RS 4
1735 Override the machine\-id set on the hard drive\&. See
1736 \fIsystemd\&.machine_id=\fR
1737 above\&.
1738 .sp
1739 Added in version 229\&.
1740 .RE
1741 .PP
1742 \fB\-\-service\-watchdogs\fR
1743 .RS 4
1744 Globally enable/disable all service watchdog timeouts and emergency actions\&. See
1745 \fIsystemd\&.service_watchdogs\fR
1746 above\&.
1747 .sp
1748 Added in version 237\&.
1749 .RE
1750 .PP
1751 \fB\-\-default\-standard\-output=\fR, \fB\-\-default\-standard\-error=\fR
1752 .RS 4
1753 Sets the default output or error output for all services and sockets, respectively\&. See
1754 \fIsystemd\&.default_standard_output=\fR
1755 and
1756 \fIsystemd\&.default_standard_error=\fR
1757 above\&.
1758 .RE
1759 .SH "SYSTEM CLOCK EPOCH"
1760 .PP
1761 When
1762 \fBsystemd\fR
1763 is started or restarted, it may set the system clock to the "epoch"\&. This mechanism is used to ensure that the system clock remains somewhat reasonably initialized and roughly monotonic across reboots, in case no battery\-backed local RTC is available or it does not work correctly\&.
1764 .PP
1765 The epoch is the lowest date above which the system clock time is assumed to be set correctly\&. When initializing, the local clock is
1766 \fIadvanced\fR
1767 to the epoch if it was set to a lower value\&. As a special case, if the local clock is sufficiently far in the future (by default 15 years, but this can be configured at build time), the hardware clock is assumed to be broken, and the system clock is
1768 \fIrewound\fR
1769 to the epoch\&.
1770 .PP
1771 The epoch is set to the highest of: the build time of
1772 systemd, the modification time ("mtime") of
1773 /usr/lib/clock\-epoch, and the modification time of
1774 /var/lib/systemd/timesync/clock\&.
1775 .SH "FILES"
1776 .PP
1777 /run/systemd/notify
1778 .RS 4
1779 Daemon status notification socket\&. This is an
1780 \fBAF_UNIX\fR
1781 datagram socket and is used to implement the daemon notification logic as implemented by
1782 \fBsd_notify\fR(3)\&.
1783 .RE
1784 .PP
1785 /run/systemd/private
1786 .RS 4
1787 Used internally as communication channel between
1788 \fBsystemctl\fR(1)
1789 and the systemd process\&. This is an
1790 \fBAF_UNIX\fR
1791 stream socket\&. This interface is private to systemd and should not be used in external projects\&.
1792 .RE
1793 .PP
1794 /usr/lib/clock\-epoch
1795 .RS 4
1796 The modification time ("mtime") of this file is used for the time epoch, see previous section\&.
1797 .sp
1798 Added in version 247\&.
1799 .RE
1800 .PP
1801 /var/lib/systemd/timesync/clock
1802 .RS 4
1803 The modification time ("mtime") of this file is updated by
1804 \fBsystemd-timesyncd.service\fR(8)\&. If present, the modification time of file is used for the epoch, see previous section\&.
1805 .sp
1806 Added in version 257\&.
1807 .RE
1808 .SH "HISTORY"
1809 .PP
1810 systemd 252
1811 .RS 4
1812 Kernel command\-line arguments
1813 \fIsystemd\&.unified_cgroup_hierarchy\fR
1814 and
1815 \fIsystemd\&.legacy_systemd_cgroup_controller\fR
1816 were deprecated\&. Please switch to the unified cgroup hierarchy\&.
1817 .RE
1818 .SH "SEE ALSO"
1819 .PP
1820 The \m[blue]\fBsystemd Homepage\fR\m[]\&\s-2\u[9]\d\s+2, \fBsystemd-system.conf\fR(5), \fBlocale.conf\fR(5), \fBsystemctl\fR(1), \fBjournalctl\fR(1), \fBsystemd-notify\fR(1), \fBdaemon\fR(7), \fBsd-daemon\fR(3), \fBorg.freedesktop.systemd1\fR(5), \fBsystemd.unit\fR(5), \fBsystemd.special\fR(7), \fBpkg-config\fR(1), \fBkernel-command-line\fR(7), \fBbootup\fR(7), \fBsystemd.directives\fR(7), \fBorg.freedesktop.systemd1\fR(5)
1821 .PP
1822 For more information about the concepts and ideas behind systemd, please refer to the
1823 \m[blue]\fBOriginal Design Document\fR\m[]\&\s-2\u[10]\d\s+2\&.
1824 .SH "NOTES"
1825 .IP " 1." 4
1826 Interface Portability and Stability Promise
1827 .RS 4
1828 \%https://systemd.io/PORTABILITY_AND_STABILITY/
1829 .RE
1830 .IP " 2." 4
1831 Container Interface
1832 .RS 4
1833 \%https://systemd.io/CONTAINER_INTERFACE
1834 .RE
1835 .IP " 3." 4
1836 initrd Interface
1837 .RS 4
1838 \%https://systemd.io/INITRD_INTERFACE/
1839 .RE
1840 .IP " 4." 4
1841 Control Groups v2
1842 .RS 4
1843 \%https://docs.kernel.org/admin-guide/cgroup-v2.html
1844 .RE
1845 .IP " 5." 4
1846 XDG Base Directory specification
1847 .RS 4
1848 \%https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html
1849 .RE
1850 .IP " 6." 4
1851 It is recommended for other tools to set and check
1852 \fI$SUDO_UID\fR
1853 as appropriate, treating it is a common interface.
1854 .IP " 7." 4
1855 Known Environment Variables
1856 .RS 4
1857 \%https://systemd.io/ENVIRONMENT
1858 .RE
1859 .IP " 8." 4
1860 System and Service Credentials
1861 .RS 4
1862 \%https://systemd.io/CREDENTIALS
1863 .RE
1864 .IP " 9." 4
1865 systemd Homepage
1866 .RS 4
1867 \%https://systemd.io/
1868 .RE
1869 .IP "10." 4
1870 Original Design Document
1871 .RS 4
1872 \%https://0pointer.de/blog/projects/systemd.html
1873 .RE