Debian Codegraph @

upstream/debian-trixie/man1/systemd.1

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