Debian Codegraph @

upstream/debian-unstable/man8/systemd-coredump.8

raw
1 '\" t
2 .TH "SYSTEMD\-COREDUMP" "8" "" "systemd 261~rc3" "systemd-coredump"
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-coredump, systemd-coredump.socket, [email protected] \- Acquire, save and process core dumps
24 .SH "SYNOPSIS"
25 .PP
26 /usr/lib/systemd/systemd\-coredump
27 .PP
28 /usr/lib/systemd/systemd\-coredump
29 \fB\-\-backtrace\fR
30 .PP
31 systemd\-coredump@\&.service
32 .PP
33 systemd\-coredump\&.socket
34 .SH "DESCRIPTION"
35 .PP
36 systemd\-coredump@\&.service
37 is a system service to process core dumps\&. It will log a summary of the event to
38 \fBsystemd-journald.service\fR(8), including information about the process identifier, owner, the signal that killed the process, and the stack trace if possible\&. It may also save the core dump for later processing\&. See the "Information about the crashed process" section below\&.
39 .PP
40 The behavior of a specific program upon reception of a signal is governed by a few factors which are described in detail in
41 \fBcore\fR(5)\&. In particular, the core dump will only be processed when the related process resource limits (\fBRLIMIT_CORE\fR) are sufficient\&.
42 .PP
43 Core dumps can be written to the journal or saved as a file\&. In both cases, they can be retrieved for further processing, for example in
44 \fBgdb\fR(1)\&. See
45 \fBcoredumpctl\fR(1), in particular the
46 \fBlist\fR
47 and
48 \fBdebug\fR
49 verbs\&.
50 .PP
51 By default,
52 \fBsystemd\-coredump\fR
53 will log the core dump to the journal, including a backtrace if possible, and store the core dump (an image of the memory contents of the process) itself in an external file in
54 /var/lib/systemd/coredump/\&. These core dumps are deleted after a few days by default; see
55 /usr/lib/tmpfiles\&.d/systemd\&.conf
56 for details\&. Note that the removal of core files from the file system and the purging of journal entries are independent, and the core file may be present without the journal entry, and journal entries may point to since\-removed core files\&. Some metadata is attached to core files in the form of extended attributes, so the core files are useful for some purposes even without the full metadata available in the journal entry\&.
57 .PP
58 For further details see
59 \m[blue]\fBsystemd Coredump Handling\fR\m[]\&\s-2\u[1]\d\s+2\&.
60 .SS "Invocation of systemd\-coredump"
61 .PP
62 The
63 \fBsystemd\-coredump\fR
64 executable does the actual work\&. It is invoked twice: once as the handler by the kernel, and the second time in the
65 systemd\-coredump@\&.service
66 to actually write the data to the journal and process and save the core file\&.
67 .PP
68 When the kernel invokes
69 \fBsystemd\-coredump\fR
70 to handle a core dump, it runs in privileged mode, and will connect to the socket created by the
71 systemd\-coredump\&.socket
72 unit, which in turn will spawn an unprivileged
73 systemd\-coredump@\&.service
74 instance to process the core dump\&. Hence
75 systemd\-coredump\&.socket
76 and
77 systemd\-coredump@\&.service
78 are helper units which do the actual processing of core dumps and are subject to normal service management\&.
79 .PP
80 It is also possible to invoke
81 \fBsystemd\-coredump\fR
82 with
83 \fB\-\-backtrace\fR
84 option\&. In this case,
85 \fBsystemd\-coredump\fR
86 expects a journal entry in the journal
87 \m[blue]\fBJournal Export Format\fR\m[]\&\s-2\u[2]\d\s+2
88 on standard input\&. The entry should contain a
89 \fIMESSAGE=\fR
90 field and any additional metadata fields the caller deems reasonable\&.
91 \fBsystemd\-coredump\fR
92 will append additional metadata fields in the same way it does for core dumps received from the kernel\&. In this mode, no core dump is stored in the journal\&.
93 .SS "Core dumps in Containers/Namespaces"
94 .PP
95 The
96 systemd\-coredump@\&.service
97 service will automatically attempt to extract a stacktrace from a process as it crashes\&. For this stacktrace symbols will be resolved based on debug information embedded in the crashing ELF image, or equivalent debug information separately available on the host OS\&. For processes that crash inside of local containers or other mount namespace\-based sandboxes, this auxiliary debug information is typically not available on the host (simply because containers typically run different software versions than the host)\&.
98 systemd\-coredump
99 provides two mechanisms to address this:
100 .sp
101 .RS 4
102 .ie n \{\
103 \h'-04' 1.\h'+01'\c
104 .\}
105 .el \{\
106 .sp -1
107 .IP " 1." 4.2
108 .\}
109 For full\-OS containers running systemd inside it is a good idea to enable
110 \fICoredumpReceive=\fR
111 on the unit (see
112 \fBsystemd.resource-control\fR(5)), which ensures that coredumps of a container are attempted to be forwarded to
113 systemd\-coredump@\&.service
114 running inside the container, i\&.e the container gets to process and store its own core dumps\&. Note that
115 \fBsystemd-nspawn\fR(8)
116 defaults to this mode if invoked with the
117 \fB\-\-boot\fR
118 switch\&. This mode of operation is generally recommended for security reasons: the security\-sensitive processing of the core dump is done within the confinements of the container itself, by the container\*(Aqs own code, backed by the container\*(Aqs own storage\&.
119 .RE
120 .sp
121 .RS 4
122 .ie n \{\
123 \h'-04' 2.\h'+01'\c
124 .\}
125 .el \{\
126 .sp -1
127 .IP " 2." 4.2
128 .\}
129 Alternatively, for more restricted containers (that do not run a proper
130 init
131 system as PID 1) it is possible to enable processing of the core dump on the host, with access to the debug information data from the container itself\&. This mode of operation must be enabled via
132 \fIEnterNamespace=\fR
133 in
134 \fBcoredump.conf\fR(5), and defaults to off, for security reasons\&.
135 .RE
136 .PP
137 If both
138 \fICoredumpReceive=\fR
139 is enabled on the unit of the container the core dump belongs to, and
140 \fIEnterNamespace=\fR
141 is enabled in the
142 coredump\&.conf
143 configuration file, the former takes precedence\&.
144 .SH "CONFIGURATION"
145 .PP
146 For programs started by
147 \fBsystemd\fR, process resource limits can be set by directive
148 \fILimitCORE=\fR, see
149 \fBsystemd.exec\fR(5)\&.
150 .PP
151 In order to be used by the kernel to handle core dumps,
152 \fBsystemd\-coredump\fR
153 must be configured in
154 \fBsysctl\fR(8)
155 parameter
156 \fIkernel\&.core_pattern\fR\&. The syntax of this parameter is explained in
157 \fBcore\fR(5)\&. systemd installs the file
158 /usr/lib/sysctl\&.d/50\-coredump\&.conf
159 which configures
160 \fIkernel\&.core_pattern\fR
161 accordingly\&. This file may be masked or overridden to use a different setting following normal
162 \fBsysctl.d\fR(5)
163 rules\&. If the sysctl configuration is modified, it must be updated in the kernel before it takes effect, see
164 \fBsysctl\fR(8)
165 and
166 \fBsystemd-sysctl\fR(8)\&.
167 .PP
168 In order to be used in the
169 \fB\-\-backtrace\fR
170 mode, an appropriate backtrace handler must be installed on the sender side\&. For example, in case of
171 \fBpython\fR(1), this means a
172 \fIsys\&.excepthook\fR
173 must be installed, see
174 \m[blue]\fBsystemd\-coredump\-python\fR\m[]\&\s-2\u[3]\d\s+2\&.
175 .PP
176 The behavior of
177 \fBsystemd\-coredump\fR
178 itself is configured through the configuration file
179 /etc/systemd/coredump\&.conf
180 and corresponding snippets
181 /etc/systemd/coredump\&.conf\&.d/*\&.conf, see
182 \fBcoredump.conf\fR(5)\&. A new instance of
183 \fBsystemd\-coredump\fR
184 is invoked upon receiving every core dump\&. Therefore, changes in these files will take effect the next time a core dump is received\&.
185 .PP
186 Resources used by core dump files are restricted in two ways\&. Parameters like maximum size of acquired core dumps and files can be set in files
187 /etc/systemd/coredump\&.conf
188 and snippets mentioned above\&. In addition the storage time of core dump files is restricted by
189 \fBsystemd\-tmpfiles\fR, corresponding settings are by default in
190 /usr/lib/tmpfiles\&.d/systemd\&.conf\&. The default is to delete core dumps after a few days; see the above file for details\&.
191 .SS "Disabling coredump processing"
192 .PP
193 To disable potentially resource\-intensive processing by
194 \fBsystemd\-coredump\fR, set
195 .sp
196 .if n \{\
197 .RS 4
198 .\}
199 .nf
200 Storage=none
201 ProcessSizeMax=0
202 .fi
203 .if n \{\
204 .RE
205 .\}
206 .sp
207 in
208 \fBcoredump.conf\fR(5)\&.
209 .SH "INFORMATION ABOUT THE CRASHED PROCESS"
210 .PP
211 \fBcoredumpctl\fR(1)
212 can be used to retrieve saved core dumps independently of their location, to display information, and to process them e\&.g\&. by passing to the GNU debugger (gdb)\&.
213 .PP
214 Data stored in the journal can be also viewed with
215 \fBjournalctl\fR(1)
216 as usual (or from any other process, using the
217 \fBsd-journal\fR(3)
218 API)\&. The relevant messages have
219 \fBMESSAGE_ID=fc2e22bc6ee647b6b90729ab34a250b1\fR:
220 .sp
221 .if n \{\
222 .RS 4
223 .\}
224 .nf
225 $ journalctl MESSAGE_ID=fc2e22bc6ee647b6b90729ab34a250b1 \-o verbose
226 \&...
227 MESSAGE_ID=fc2e22bc6ee647b6b90729ab34a250b1
228 COREDUMP_PID=552351
229 COREDUMP_UID=1000
230 COREDUMP_GID=1000
231 COREDUMP_SIGNAL_NAME=SIGSEGV
232 COREDUMP_SIGNAL=11
233 COREDUMP_CODE=2
234 COREDUMP_TIMESTAMP=1614342930000000
235 COREDUMP_COMM=Web Content
236 COREDUMP_EXE=/usr/lib64/firefox/firefox
237 COREDUMP_USER_UNIT=app\-gnome\-firefox\-552136\&.scope
238 COREDUMP_CMDLINE=/usr/lib64/firefox/firefox \-contentproc \-childID 5 \-isForBrowser \&...
239 COREDUMP_CGROUP=/user\&.slice/user\-1000\&.slice/user@1000\&.service/app\&.slice/app\-\&...\&.scope
240 COREDUMP_FILENAME=/var/lib/systemd/coredump/core\&.Web\&...\&.552351\&.\&...\&.zst
241 \&...
242 .fi
243 .if n \{\
244 .RE
245 .\}
246 .PP
247 The following fields are saved (if known) with the journal entry
248 .PP
249 \fICOREDUMP_UID=\fR, \fICOREDUMP_PID=\fR, \fICOREDUMP_GID=\fR
250 .RS 4
251 The process number (PID), owner user number (UID), and group number (GID) of the crashed process\&.
252 .sp
253 When the crashed process was part of a container (or in a process or user namespace in general), those are the values as seen
254 \fIoutside\fR, in the namespace where
255 systemd\-coredump
256 is running\&.
257 .sp
258 Added in version 248\&.
259 .RE
260 .PP
261 \fICOREDUMP_BY_PIDFD=\fR
262 .RS 4
263 If the crashed process was analyzed using a PIDFD provided by the kernel (requires kernel v6\&.16) then this field will be present and set to
264 "1"\&. If this field is not set, then the crashed process was analyzed via a PID, which is known to be subject to race conditions\&.
265 .sp
266 Added in version 258\&.
267 .RE
268 .PP
269 \fICOREDUMP_TIMESTAMP=\fR
270 .RS 4
271 The time of the crash as reported by the kernel (in μs since the epoch)\&.
272 .sp
273 Added in version 248\&.
274 .RE
275 .PP
276 \fICOREDUMP_RLIMIT=\fR
277 .RS 4
278 The core file size soft resource limit, see
279 \fBgetrlimit\fR(2)\&.
280 .sp
281 Added in version 248\&.
282 .RE
283 .PP
284 \fICOREDUMP_UNIT=\fR, \fICOREDUMP_SLICE=\fR
285 .RS 4
286 The system unit and slice names\&.
287 .sp
288 When the crashed process was in container, those are the units names
289 \fIoutside\fR, in the main system manager\&.
290 .sp
291 Added in version 248\&.
292 .RE
293 .PP
294 \fICOREDUMP_CGROUP=\fR
295 .RS 4
296 The primary cgroup of the unit of the crashed process\&.
297 .sp
298 When the crashed process was in a container, this is the full path, as seen outside of the container\&.
299 .sp
300 Added in version 248\&.
301 .RE
302 .PP
303 \fICOREDUMP_PROC_CGROUP=\fR
304 .RS 4
305 Control group information in the format used in
306 /proc/self/cgroup\&. On systems with the unified cgroup hierarchy, this is a single path prefixed with
307 "0::", and multiple paths prefixed with controller numbers on legacy systems\&.
308 .sp
309 When the crashed process was in a container, this is the full path, as seen outside of the container\&.
310 .sp
311 Added in version 248\&.
312 .RE
313 .PP
314 \fICOREDUMP_OWNER_UID=\fR, \fICOREDUMP_USER_UNIT=\fR, \fICOREDUMP_SESSION=\fR
315 .RS 4
316 The numerical UID of the user owning the login session or systemd user unit of the crashed process, the user manager unit, and the session identifier\&. All three fields are only present for user processes\&.
317 .sp
318 When the crashed process was in container, those are the values
319 \fIoutside\fR, in the main system\&.
320 .sp
321 Added in version 248\&.
322 .RE
323 .PP
324 \fICOREDUMP_SIGNAL_NAME=\fR, \fICOREDUMP_SIGNAL=\fR
325 .RS 4
326 The terminating signal name (with the
327 "SIG"
328 prefix
329 \&\s-2\u[4]\d\s+2) and numerical value\&. (Both are included because signal numbers vary by architecture\&.)
330 .sp
331 Added in version 248\&.
332 .RE
333 .PP
334 \fICOREDUMP_CODE=\fR
335 .RS 4
336 The reason why the signal was sent as a numerical value\&. The code is defined as field
337 \fIsi_code\fR
338 in the
339 \fIsiginfo_t\fR
340 structure and documented in
341 \fBsigaction\fR(2)\&.
342 .sp
343 Added in version 261\&.
344 .RE
345 .PP
346 \fICOREDUMP_CWD=\fR, \fICOREDUMP_ROOT=\fR
347 .RS 4
348 The current working directory and root directory of the crashed process\&.
349 .sp
350 When the crashed process is in a container, those paths are relative to the root of the container\*(Aqs mount namespace\&.
351 .sp
352 Added in version 248\&.
353 .RE
354 .PP
355 \fICOREDUMP_DUMPABLE=\fR
356 .RS 4
357 The
358 \fBPR_GET_DUMPABLE\fR
359 field as reported by the kernel, see
360 \fBprctl\fR(2)\&.
361 .sp
362 Added in version 258\&.
363 .RE
364 .PP
365 \fICOREDUMP_OPEN_FDS=\fR
366 .RS 4
367 Information about open file descriptors, in the following format:
368 .sp
369 .if n \{\
370 .RS 4
371 .\}
372 .nf
373 \fIfd\fR:\fI/path/to/file\fR
374 pos: \&.\&.\&.
375 flags: \&.\&.\&.
376 \&.\&.\&.
377
378 \fIfd\fR:\fI/path/to/file\fR
379 pos: \&.\&.\&.
380 flags: \&.\&.\&.
381 \&.\&.\&.
382 .fi
383 .if n \{\
384 .RE
385 .\}
386 .sp
387 The first line contains the file descriptor number
388 \fIfd\fR
389 and the path, while subsequent lines show the contents of
390 /proc/\fIpid\fR/fdinfo/\fIfd\fR\&.
391 .sp
392 Added in version 248\&.
393 .RE
394 .PP
395 \fICOREDUMP_EXE=\fR
396 .RS 4
397 The destination of the
398 /proc/\fIpid\fR/exe
399 symlink\&.
400 .sp
401 When the crashed process is in a container, that path is relative to the root of the container\*(Aqs mount namespace\&.
402 .sp
403 Added in version 248\&.
404 .RE
405 .PP
406 \fICOREDUMP_CMDLINE=\fR, \fICOREDUMP_COMM=\fR, \fICOREDUMP_ENVIRON=\fR, \fICOREDUMP_PROC_AUXV=\fR, \fICOREDUMP_PROC_LIMITS=\fR, \fICOREDUMP_PROC_MAPS=\fR, \fICOREDUMP_PROC_MOUNTINFO=\fR, \fICOREDUMP_PROC_STATUS=\fR
407 .RS 4
408 Fields that map the per\-process entries in the
409 /proc/
410 filesystem:
411 /proc/\fIpid\fR/cmdline
412 (the command line of the crashed process),
413 /proc/\fIpid\fR/comm
414 (the command name associated with the process),
415 /proc/\fIpid\fR/environ
416 (the environment block of the crashed process),
417 /proc/\fIpid\fR/auxv
418 (the auxiliary vector of the crashed process, see
419 \fBgetauxval\fR(3)),
420 /proc/\fIpid\fR/limits
421 (the soft and hard resource limits),
422 /proc/\fIpid\fR/maps
423 (memory regions visible to the process and their access permissions),
424 /proc/\fIpid\fR/mountinfo
425 (mount points in the process\*(Aqs mount namespace),
426 /proc/\fIpid\fR/status
427 (various metadata about the process)\&.
428 .sp
429 See
430 \fBproc\fR(5)
431 for more information\&.
432 .sp
433 Added in version 248\&.
434 .RE
435 .PP
436 \fICOREDUMP_HOSTNAME=\fR
437 .RS 4
438 The system hostname\&.
439 .sp
440 When the crashed process was in container, this is the container hostname\&.
441 .sp
442 Added in version 248\&.
443 .RE
444 .PP
445 \fICOREDUMP_CONTAINER_CMDLINE=\fR
446 .RS 4
447 For processes running in a container, the command line of the process spawning the container (the first parent process with a different mount namespace)\&.
448 .sp
449 Added in version 248\&.
450 .RE
451 .PP
452 \fICOREDUMP=\fR
453 .RS 4
454 When the core is stored in the journal, the core image itself\&.
455 .sp
456 Added in version 248\&.
457 .RE
458 .PP
459 \fICOREDUMP_FILENAME=\fR
460 .RS 4
461 When the core is stored externally, the path to the core file\&.
462 .sp
463 Added in version 248\&.
464 .RE
465 .PP
466 \fICOREDUMP_TRUNCATED=\fR
467 .RS 4
468 Set to
469 "1"
470 when the saved coredump was truncated\&. (A partial core image may still be processed by some tools, though obviously not all information is available\&.)
471 .sp
472 Added in version 248\&.
473 .RE
474 .PP
475 \fICOREDUMP_PACKAGE_NAME=\fR, \fICOREDUMP_PACKAGE_VERSION=\fR, \fICOREDUMP_PACKAGE_JSON=\fR
476 .RS 4
477 If the executable contained \&.package metadata ELF notes, they will be parsed and attached\&. The
478 \fIpackage\fR
479 and
480 \fIversion\fR
481 of the \*(Aqmain\*(Aq ELF module (i\&.e\&., the executable) will be appended individually\&. The JSON\-formatted content of all modules will be appended as a single JSON object, each with the module name as the key\&. For more information about this metadata format and content, see the
482 \m[blue]\fBPackage Metadata for Executable Files\fR\m[]\&\s-2\u[5]\d\s+2
483 document\&.
484 .sp
485 Added in version 249\&.
486 .RE
487 .PP
488 \fIMESSAGE=\fR
489 .RS 4
490 The message generated by
491 \fBsystemd\-coredump\fR
492 that includes the backtrace if it was successfully generated\&. When
493 \fBsystemd\-coredump\fR
494 is invoked with
495 \fB\-\-backtrace\fR, this field is provided by the caller\&.
496 .sp
497 Added in version 248\&.
498 .RE
499 .PP
500 Various other fields exist in the journal entry, but pertain to the logging process, i\&.e\&.
501 \fBsystemd\-coredump\fR, not the crashed process\&. See
502 \fBsystemd.journal-fields\fR(7)\&.
503 .PP
504 The following fields are saved (if known) with the external file listed in
505 \fICOREDUMP_FILENAME=\fR
506 as extended attributes:
507 .PP
508 \fIuser\&.coredump\&.pid\fR, \fIuser\&.coredump\&.uid\fR, \fIuser\&.coredump\&.gid\fR, \fIuser\&.coredump\&.signal\fR, \fIuser\&.coredump\&.timestamp\fR, \fIuser\&.coredump\&.rlimit\fR, \fIuser\&.coredump\&.hostname\fR, \fIuser\&.coredump\&.comm\fR, \fIuser\&.coredump\&.exe\fR
509 .RS 4
510 Those are the same as
511 \fICOREDUMP_PID=\fR,
512 \fICOREDUMP_UID=\fR,
513 \fICOREDUMP_GID=\fR,
514 \fICOREDUMP_SIGNAL=\fR,
515 \fICOREDUMP_TIMESTAMP=\fR,
516 \fICOREDUMP_RLIMIT=\fR,
517 \fICOREDUMP_HOSTNAME=\fR,
518 \fICOREDUMP_COMM=\fR, and
519 \fICOREDUMP_EXE=\fR, described above\&.
520 .sp
521 Added in version 248\&.
522 .RE
523 .PP
524 Those can be viewed using
525 \fBgetfattr\fR(1)\&. For the core file described in the journal entry shown above:
526 .sp
527 .if n \{\
528 .RS 4
529 .\}
530 .nf
531 $ getfattr \-\-absolute\-names \-d /var/lib/systemd/coredump/core\&.Web\&...\&.552351\&.\&...\&.zst
532 # file: /var/lib/systemd/coredump/core\&.Web\&...\&.552351\&.\&...\&.zst
533 user\&.coredump\&.pid="552351"
534 user\&.coredump\&.uid="1000"
535 user\&.coredump\&.gid="1000"
536 user\&.coredump\&.signal="11"
537 user\&.coredump\&.timestamp="1614342930000000"
538 user\&.coredump\&.comm="Web Content"
539 user\&.coredump\&.exe="/usr/lib64/firefox/firefox"
540 \&...
541 .fi
542 .if n \{\
543 .RE
544 .\}
545 .sp
546 .SH "SEE ALSO"
547 .PP
548 \fBcoredump.conf\fR(5), \fBcoredumpctl\fR(1), \fBsystemd-journald.service\fR(8), \fBsystemd-tmpfiles\fR(8), \fBcore\fR(5), \fBsysctl.d\fR(5), \fBsystemd-sysctl.service\fR(8), \m[blue]\fBsystemd Coredump Handling\fR\m[]\&\s-2\u[1]\d\s+2
549 .SH "NOTES"
550 .IP " 1." 4
551 systemd Coredump Handling
552 .RS 4
553 \%https://systemd.io/COREDUMP
554 .RE
555 .IP " 2." 4
556 Journal Export Format
557 .RS 4
558 \%https://systemd.io/JOURNAL_EXPORT_FORMATS#journal-export-format
559 .RE
560 .IP " 3." 4
561 systemd-coredump-python
562 .RS 4
563 \%https://github.com/systemd/systemd-coredump-python
564 .RE
565 .IP " 4." 4
566 \fBkill\fR(1)
567 expects signal names
568 \fIwithout\fR
569 the prefix;
570 \fBkill\fR(2)
571 uses the prefix; all systemd tools accept signal names both with and without the prefix.
572 .IP " 5." 4
573 Package Metadata for Executable Files
574 .RS 4
575 \%https://systemd.io/PACKAGE_METADATA_FOR_EXECUTABLE_FILES/
576 .RE