Debian Codegraph @

upstream/debian-trixie/man8/systemd-tmpfiles.8

raw
1 '\" t
2 .TH "SYSTEMD\-TMPFILES" "8" "" "systemd 257.13" "systemd-tmpfiles"
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-tmpfiles, systemd-tmpfiles-setup.service, systemd-tmpfiles-setup-dev-early.service, systemd-tmpfiles-setup-dev.service, systemd-tmpfiles-clean.service, systemd-tmpfiles-clean.timer \- Create, delete, and clean up files and directories
24 .SH "SYNOPSIS"
25 .HP \w'\fBsystemd\-tmpfiles\fR\ 'u
26 \fBsystemd\-tmpfiles\fR [OPTIONS...] [\fICONFIGFILE\fR...]
27 .PP
28 System units:
29 .RS 4
30 systemd\-tmpfiles\-setup\&.service
31 .RE
32 .RS 4
33 systemd\-tmpfiles\-setup\-dev\-early\&.service
34 .RE
35 .RS 4
36 systemd\-tmpfiles\-setup\-dev\&.service
37 .RE
38 .RS 4
39 systemd\-tmpfiles\-clean\&.service
40 .RE
41 .RS 4
42 systemd\-tmpfiles\-clean\&.timer
43 .RE
44 .PP
45 User units:
46 .RS 4
47 systemd\-tmpfiles\-setup\&.service
48 .RE
49 .RS 4
50 systemd\-tmpfiles\-clean\&.service
51 .RE
52 .RS 4
53 systemd\-tmpfiles\-clean\&.timer
54 .RE
55 .SH "DESCRIPTION"
56 .PP
57 \fBsystemd\-tmpfiles\fR
58 creates, deletes, and cleans up files and directories, using the configuration file format and location specified in
59 \fBtmpfiles.d\fR(5)\&. Historically, it was designed to manage volatile and temporary files, as the name suggests, but it provides generic file management functionality and can be used to manage any kind of files\&. It must be invoked with one or more commands
60 \fB\-\-create\fR,
61 \fB\-\-remove\fR, and
62 \fB\-\-clean\fR, to select the respective subset of operations\&.
63 .PP
64 If invoked with no arguments, directives from the configuration files found in the directories specified by
65 \fBtmpfiles.d\fR(5)
66 are executed\&. When invoked with positional arguments, if option
67 \fB\-\-replace=\fR\fB\fIPATH\fR\fR
68 is specified, arguments specified on the command line are used instead of the configuration file
69 \fIPATH\fR\&. Otherwise, just the configuration specified by the command line arguments is executed\&. If the string
70 "\-"
71 is specified instead of a filename, the configuration is read from standard input\&. If the argument is a file name (without any slashes), all configuration directories are searched for a matching file and the file found that has the highest priority is executed\&. If the argument is a path, that file is used directly without searching the configuration directories for any other matching file\&.
72 .PP
73 System services (systemd\-tmpfiles\-setup\&.service,
74 systemd\-tmpfiles\-setup\-dev\-early\&.service,
75 systemd\-tmpfiles\-setup\-dev\&.service,
76 systemd\-tmpfiles\-clean\&.service) invoke
77 \fBsystemd\-tmpfiles\fR
78 to create system files and to perform system wide cleanup\&. Those services read administrator\-controlled configuration files in
79 tmpfiles\&.d/
80 directories\&. User services (systemd\-tmpfiles\-setup\&.service,
81 systemd\-tmpfiles\-clean\&.service) also invoke
82 \fBsystemd\-tmpfiles\fR, but it reads a separate set of files, which includes user\-controlled files under
83 ~/\&.config/user\-tmpfiles\&.d/
84 and
85 ~/\&.local/share/user\-tmpfiles\&.d/, and administrator\-controlled files under
86 /usr/share/user\-tmpfiles\&.d/\&. Users may use this to create and clean up files under their control, but the system instance performs global cleanup and is not influenced by user configuration\&. Note that this means a time\-based cleanup configured in the system instance, such as the one typically configured for
87 /tmp/, will thus also affect files created by the user instance if they are placed in
88 /tmp/, even if the user instance\*(Aqs time\-based cleanup is turned off\&.
89 .PP
90 To re\-apply settings after configuration has been modified, simply restart
91 systemd\-tmpfiles\-clean\&.service, which will apply any settings which can be safely executed at runtime\&. To debug
92 \fBsystemd\-tmpfiles\fR, it may be useful to invoke it directly from the command line with increased log level (see
93 \fI$SYSTEMD_LOG_LEVEL\fR
94 below)\&.
95 .SH "COMMANDS AND OPTIONS"
96 .PP
97 The following commands are understood:
98 .PP
99 \fB\-\-create\fR
100 .RS 4
101 If this command is passed, all files and directories marked with
102 \fIf\fR,
103 \fIF\fR,
104 \fIw\fR,
105 \fId\fR,
106 \fID\fR,
107 \fIv\fR,
108 \fIp\fR,
109 \fIL\fR,
110 \fIc\fR,
111 \fIb\fR,
112 \fIm\fR
113 in the configuration files are created or written to\&. Files and directories marked with
114 \fIz\fR,
115 \fIZ\fR,
116 \fIt\fR,
117 \fIT\fR,
118 \fIa\fR, and
119 \fIA\fR
120 have their ownership, access mode and security labels set\&.
121 .RE
122 .PP
123 \fB\-\-clean\fR
124 .RS 4
125 If this command is passed, all files and directories with an age parameter configured will be cleaned up\&.
126 .RE
127 .PP
128 \fB\-\-remove\fR
129 .RS 4
130 If this command is passed, the contents of directories marked with
131 \fID\fR
132 or
133 \fIR\fR, and files or directories themselves marked with
134 \fIr\fR
135 or
136 \fIR\fR
137 are removed unless an exclusive or shared BSD lock is taken on them (see
138 \fBflock\fR(2))\&.
139 .RE
140 .PP
141 \fB\-\-purge\fR
142 .RS 4
143 If this option is passed, all files and directories declared for
144 \fIcreation\fR
145 and marked with the
146 "$"
147 character by the
148 tmpfiles\&.d/
149 files specified on the command line will be
150 \fIdeleted\fR\&. Specifically, this acts on all files and directories marked with
151 \fIf\fR,
152 \fIF\fR,
153 \fId\fR,
154 \fID\fR,
155 \fIv\fR,
156 \fIq\fR,
157 \fIQ\fR,
158 \fIp\fR,
159 \fIL\fR,
160 \fIc\fR,
161 \fIb\fR,
162 \fIC\fR,
163 \fIw\fR,
164 \fIe\fR\&. If this switch is used at least one
165 tmpfiles\&.d/
166 file (or
167 \-
168 for standard input) must be specified on the command line or the invocation will be refused, for safety reasons (as otherwise much of the installed system files might be removed)\&.
169 .sp
170 The primary usecase for this option is to automatically remove files and directories that originally have been created on behalf of an installed package at package removal time\&.
171 .sp
172 It is recommended to first run this command in combination with
173 \fB\-\-dry\-run\fR
174 (see below) to verify which files and directories will be deleted\&.
175 .sp
176 \fIWarning!\fR
177 This is usually not the command you want! In most cases
178 \fB\-\-remove\fR
179 is what you are looking for\&.
180 .sp
181 Added in version 256\&.
182 .RE
183 .PP
184 \fB\-\-user\fR
185 .RS 4
186 Execute "user" configuration, i\&.e\&.
187 tmpfiles\&.d/
188 files in user configuration directories\&.
189 .sp
190 Added in version 236\&.
191 .RE
192 .PP
193 \fB\-\-boot\fR
194 .RS 4
195 Also execute lines with an exclamation mark\&. Lines that are not safe to be executed on a running system may be marked in this way\&.
196 \fBsystemd\-tmpfiles\fR
197 is executed in early boot with
198 \fB\-\-boot\fR
199 specified and will execute those lines\&. When invoked again later, it should be called without
200 \fB\-\-boot\fR\&.
201 .sp
202 Added in version 209\&.
203 .RE
204 .PP
205 \fB\-\-graceful\fR
206 .RS 4
207 Ignore configuration lines pertaining to unknown users or groups\&. This option is intended to be used in early boot before all users or groups have been created\&.
208 .sp
209 Added in version 254\&.
210 .RE
211 .PP
212 \fB\-\-dry\-run\fR
213 .RS 4
214 Process the configuration and print what operations would be performed, but do not actually change anything in the file system\&.
215 .sp
216 Added in version 256\&.
217 .RE
218 .PP
219 \fB\-\-prefix=\fR\fB\fIpath\fR\fR
220 .RS 4
221 Only apply rules with paths that start with the specified prefix\&. This option can be specified multiple times\&.
222 .sp
223 Added in version 212\&.
224 .RE
225 .PP
226 \fB\-\-exclude\-prefix=\fR\fB\fIpath\fR\fR
227 .RS 4
228 Ignore rules with paths that start with the specified prefix\&. This option can be specified multiple times\&.
229 .sp
230 Added in version 207\&.
231 .RE
232 .PP
233 \fB\-E\fR
234 .RS 4
235 A shortcut for
236 "\-\-exclude\-prefix=/dev \-\-exclude\-prefix=/proc \-\-exclude\-prefix=/run \-\-exclude\-prefix=/sys", i\&.e\&. exclude the hierarchies typically backed by virtual or memory file systems\&. This is useful in combination with
237 \fB\-\-root=\fR, if the specified directory tree contains an OS tree without these virtual/memory file systems mounted in, as it is typically not desirable to create any files and directories below these subdirectories if they are supposed to be overmounted during runtime\&.
238 .sp
239 Added in version 247\&.
240 .RE
241 .PP
242 \fB\-\-root=\fR\fB\fIroot\fR\fR
243 .RS 4
244 Takes a directory path as an argument\&. All paths will be prefixed with the given alternate
245 \fIroot\fR
246 path, including config search paths\&.
247 .sp
248 When this option is used, the libc Name Service Switch (NSS) is bypassed for resolving users and groups\&. Instead the files
249 /etc/passwd
250 and
251 /etc/group
252 inside the alternate root are read directly\&. This means that users/groups not listed in these files will not be resolved, i\&.e\&. LDAP NIS and other complex databases are not considered\&.
253 .sp
254 Consider combining this with
255 \fB\-E\fR
256 to ensure the invocation does not create files or directories below mount points in the OS image operated on that are typically overmounted during runtime\&.
257 .sp
258 Added in version 212\&.
259 .RE
260 .PP
261 \fB\-\-image=\fR\fB\fIimage\fR\fR
262 .RS 4
263 Takes a path to a disk image file or block device node\&. If specified all operations are applied to file system in the indicated disk image\&. This is similar to
264 \fB\-\-root=\fR
265 but operates on file systems stored in disk images or block devices\&. The disk image should either contain just a file system or a set of file systems within a GPT partition table, following the
266 \m[blue]\fBDiscoverable Partitions Specification\fR\m[]\&\s-2\u[1]\d\s+2\&. For further information on supported disk images, see
267 \fBsystemd-nspawn\fR(1)\*(Aqs switch of the same name\&.
268 .sp
269 Implies
270 \fB\-E\fR\&.
271 .sp
272 Added in version 247\&.
273 .RE
274 .PP
275 \fB\-\-image\-policy=\fR\fB\fIpolicy\fR\fR
276 .RS 4
277 Takes an image policy string as argument, as per
278 \fBsystemd.image-policy\fR(7)\&. The policy is enforced when operating on the disk image specified via
279 \fB\-\-image=\fR, see above\&. If not specified, defaults to the
280 "*"
281 policy, i\&.e\&. all recognized file systems in the image are used\&.
282 .RE
283 .PP
284 \fB\-\-replace=\fR\fB\fIPATH\fR\fR
285 .RS 4
286 When this option is given, one or more positional arguments must be specified\&. All configuration files found in the directories listed in
287 \fBtmpfiles.d\fR(5)
288 will be read, and the configuration given on the command line will be handled instead of and with the same priority as the configuration file
289 \fIPATH\fR\&.
290 .sp
291 This option is intended to be used when package installation scripts are running and files belonging to that package are not yet available on disk, so their contents must be given on the command line, but the admin configuration might already exist and should be given higher priority\&.
292 .sp
293 Added in version 238\&.
294 .RE
295 .PP
296 \fB\-\-cat\-config\fR
297 .RS 4
298 Copy the contents of config files to standard output\&. Before each file, the filename is printed as a comment\&.
299 .RE
300 .PP
301 \fB\-\-tldr\fR
302 .RS 4
303 Copy the contents of config files to standard output\&. Only the "interesting" parts of the configuration files are printed, comments and empty lines are skipped\&. Before each file, the filename is printed as a comment\&.
304 .RE
305 .PP
306 \fB\-\-no\-pager\fR
307 .RS 4
308 Do not pipe output into a pager\&.
309 .RE
310 .PP
311 \fB\-h\fR, \fB\-\-help\fR
312 .RS 4
313 Print a short help text and exit\&.
314 .RE
315 .PP
316 \fB\-\-version\fR
317 .RS 4
318 Print a short version string and exit\&.
319 .RE
320 .PP
321 It is possible to combine
322 \fB\-\-create\fR,
323 \fB\-\-clean\fR, and
324 \fB\-\-remove\fR
325 in one invocation (in which case removal and cleanup are executed before creation of new files)\&. For example, during boot the following command line is executed to ensure that all temporary and volatile directories are removed and created according to the configuration file:
326 .sp
327 .if n \{\
328 .RS 4
329 .\}
330 .nf
331 systemd\-tmpfiles \-\-remove \-\-create
332 .fi
333 .if n \{\
334 .RE
335 .\}
336 .SH "CREDENTIALS"
337 .PP
338 \fBsystemd\-tmpfiles\fR
339 supports the service credentials logic as implemented by
340 \fIImportCredential=\fR/\fILoadCredential=\fR/\fISetCredential=\fR
341 (see
342 \fBsystemd.exec\fR(5)
343 for details)\&. The following credentials are used when passed in:
344 .PP
345 \fItmpfiles\&.extra\fR
346 .RS 4
347 The contents of this credential may contain additional lines to operate on\&. The credential contents should follow the same format as any other
348 tmpfiles\&.d/
349 drop\-in configuration file\&. If this credential is passed it is processed after all of the drop\-in files read from the file system\&. The lines in the credential can hence augment existing lines of the OS, but not override them\&.
350 .sp
351 Added in version 252\&.
352 .RE
353 .PP
354 Note that by default the
355 systemd\-tmpfiles\-setup\&.service
356 unit file (and related unit files) is set up to inherit the
357 "tmpfiles\&.extra"
358 credential from the service manager\&.
359 .SH "ENVIRONMENT"
360 .PP
361 \fI$SYSTEMD_LOG_LEVEL\fR
362 .RS 4
363 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)
364 \fBemerg\fR,
365 \fBalert\fR,
366 \fBcrit\fR,
367 \fBerr\fR,
368 \fBwarning\fR,
369 \fBnotice\fR,
370 \fBinfo\fR,
371 \fBdebug\fR, or an integer in the range 0\&...7\&. See
372 \fBsyslog\fR(3)
373 for more information\&. Each value may optionally be prefixed with one of
374 \fBconsole\fR,
375 \fBsyslog\fR,
376 \fBkmsg\fR
377 or
378 \fBjournal\fR
379 followed by a colon to set the maximum log level for that specific log target (e\&.g\&.
380 \fBSYSTEMD_LOG_LEVEL=debug,console:info\fR
381 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\&.
382 .RE
383 .PP
384 \fI$SYSTEMD_LOG_COLOR\fR
385 .RS 4
386 A boolean\&. If true, messages written to the tty will be colored according to priority\&.
387 .sp
388 This setting is only useful when messages are written directly to the terminal, because
389 \fBjournalctl\fR(1)
390 and other tools that display logs will color messages based on the log level on their own\&.
391 .RE
392 .PP
393 \fI$SYSTEMD_LOG_TIME\fR
394 .RS 4
395 A boolean\&. If true, console log messages will be prefixed with a timestamp\&.
396 .sp
397 This setting is only useful when messages are written directly to the terminal or a file, because
398 \fBjournalctl\fR(1)
399 and other tools that display logs will attach timestamps based on the entry metadata on their own\&.
400 .RE
401 .PP
402 \fI$SYSTEMD_LOG_LOCATION\fR
403 .RS 4
404 A boolean\&. If true, messages will be prefixed with a filename and line number in the source code where the message originates\&.
405 .sp
406 Note that the log location is often attached as metadata to journal entries anyway\&. Including it directly in the message text can nevertheless be convenient when debugging programs\&.
407 .RE
408 .PP
409 \fI$SYSTEMD_LOG_TARGET\fR
410 .RS 4
411 The destination for log messages\&. One of
412 \fBconsole\fR
413 (log to the attached tty),
414 \fBconsole\-prefixed\fR
415 (log to the attached tty but with prefixes encoding the log level and "facility", see
416 \fBsyslog\fR(3),
417 \fBkmsg\fR
418 (log to the kernel circular log buffer),
419 \fBjournal\fR
420 (log to the journal),
421 \fBjournal\-or\-kmsg\fR
422 (log to the journal if available, and to kmsg otherwise),
423 \fBauto\fR
424 (determine the appropriate log target automatically, the default),
425 \fBnull\fR
426 (disable log output)\&.
427 .RE
428 .PP
429 \fI$SYSTEMD_PAGER\fR, \fI$PAGER\fR
430 .RS 4
431 Pager to use when
432 \fB\-\-no\-pager\fR
433 is not given\&.
434 \fI$SYSTEMD_PAGER\fR
435 is used if set; otherwise
436 \fI$PAGER\fR
437 is used\&. If neither
438 \fI$SYSTEMD_PAGER\fR
439 nor
440 \fI$PAGER\fR
441 are set, a set of well\-known pager implementations is tried in turn, including
442 \fBless\fR(1)
443 and
444 \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
445 "cat"
446 is equivalent to passing
447 \fB\-\-no\-pager\fR\&.
448 .sp
449 Note: if
450 \fI$SYSTEMD_PAGERSECURE\fR
451 is not set,
452 \fI$SYSTEMD_PAGER\fR
453 and
454 \fI$PAGER\fR
455 can only be used to disable the pager (with
456 "cat"
457 or
458 ""), and are otherwise ignored\&.
459 .RE
460 .PP
461 \fI$SYSTEMD_LESS\fR
462 .RS 4
463 Override the options passed to
464 \fBless\fR
465 (by default
466 "FRSXMK")\&.
467 .sp
468 Users might want to change two options in particular:
469 .PP
470 \fBK\fR
471 .RS 4
472 This option instructs the pager to exit immediately when
473 Ctrl+C
474 is pressed\&. To allow
475 \fBless\fR
476 to handle
477 Ctrl+C
478 itself to switch back to the pager command prompt, unset this option\&.
479 .sp
480 If the value of
481 \fI$SYSTEMD_LESS\fR
482 does not include
483 "K", and the pager that is invoked is
484 \fBless\fR,
485 Ctrl+C
486 will be ignored by the executable, and needs to be handled by the pager\&.
487 .RE
488 .PP
489 \fBX\fR
490 .RS 4
491 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\&.
492 .RE
493 .sp
494 Note that setting the regular
495 \fI$LESS\fR
496 environment variable has no effect for
497 \fBless\fR
498 invocations by systemd tools\&.
499 .sp
500 See
501 \fBless\fR(1)
502 for more discussion\&.
503 .RE
504 .PP
505 \fI$SYSTEMD_LESSCHARSET\fR
506 .RS 4
507 Override the charset passed to
508 \fBless\fR
509 (by default
510 "utf\-8", if the invoking terminal is determined to be UTF\-8 compatible)\&.
511 .sp
512 Note that setting the regular
513 \fI$LESSCHARSET\fR
514 environment variable has no effect for
515 \fBless\fR
516 invocations by systemd tools\&.
517 .RE
518 .PP
519 \fI$SYSTEMD_PAGERSECURE\fR
520 .RS 4
521 Common pager commands like
522 \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
523 \fBsudo\fR(8)
524 or
525 \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,
526 \fIif the pager supports that\fR
527 (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
528 \fB\-\-no\-pager\fR
529 or
530 \fIPAGER=cat\fR
531 when allowing untrusted users to execute commands with elevated privileges\&.
532 .sp
533 This option takes a boolean argument\&. When set to true, the "secure mode" of the pager is enabled\&. In "secure mode",
534 \fBLESSSECURE=1\fR
535 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
536 \fBless\fR(1)
537 is known to understand this variable and implement "secure mode"\&.
538 .sp
539 When set to false, no limitation is placed on the pager\&. Setting
540 \fISYSTEMD_PAGERSECURE=0\fR
541 or not removing it from the inherited environment may allow the user to invoke arbitrary commands\&.
542 .sp
543 When
544 \fI$SYSTEMD_PAGERSECURE\fR
545 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
546 \fBgeteuid\fR(2)
547 and
548 \fBsd_pid_get_owner_uid\fR(3), or when running under
549 \fBsudo\fR(8)
550 or similar tools (\fI$SUDO_UID\fR
551 is set
552 \&\s-2\u[2]\d\s+2)\&. In those cases,
553 \fISYSTEMD_PAGERSECURE=1\fR
554 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
555 \fI$SYSTEMD_PAGERSECURE\fR
556 or disable the pager\&.
557 .sp
558 Note that if the
559 \fI$SYSTEMD_PAGER\fR
560 or
561 \fI$PAGER\fR
562 variables are to be honoured, other than to disable the pager,
563 \fI$SYSTEMD_PAGERSECURE\fR
564 must be set too\&.
565 .RE
566 .PP
567 \fI$SYSTEMD_COLORS\fR
568 .RS 4
569 Takes a boolean argument\&. When true,
570 \fBsystemd\fR
571 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:
572 "16",
573 "256"
574 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
575 \fI$TERM\fR
576 and what the console is connected to\&.
577 .RE
578 .PP
579 \fI$SYSTEMD_URLIFY\fR
580 .RS 4
581 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
582 \fBsystemd\fR
583 makes based on
584 \fI$TERM\fR
585 and other conditions\&.
586 .RE
587 .SH "UNPRIVILEGED \-\-CLEANUP OPERATION"
588 .PP
589 \fBsystemd\-tmpfiles\fR
590 tries to avoid changing the access and modification times on the directories it accesses, which requires
591 \fBCAP_FOWNER\fR
592 privileges\&. When running as non\-root, directories which are checked for files to clean up will have their access time bumped, which might prevent their cleanup\&.
593 .SH "EXIT STATUS"
594 .PP
595 On success, 0 is returned\&. If the configuration was syntactically invalid (syntax errors, missing arguments, \&...), so some lines had to be ignored, but no other errors occurred,
596 \fB65\fR
597 is returned (\fBEX_DATAERR\fR
598 from
599 /usr/include/sysexits\&.h)\&. If the configuration was syntactically valid, but could not be executed (lack of permissions, creation of files in missing directories, invalid contents when writing to
600 /sys/
601 values, \&...),
602 \fB73\fR
603 is returned (\fBEX_CANTCREAT\fR
604 from
605 /usr/include/sysexits\&.h)\&. Otherwise,
606 \fB1\fR
607 is returned (\fBEXIT_FAILURE\fR
608 from
609 /usr/include/stdlib\&.h)\&.
610 .PP
611 Note: when creating items, if the target already exists, but is of the wrong type or otherwise does not match the requested state, and forced operation has not been requested with
612 "+", a message is emitted, but the failure is otherwise ignored\&.
613 .SH "SEE ALSO"
614 .PP
615 \fBsystemd\fR(1), \fBtmpfiles.d\fR(5)
616 .SH "NOTES"
617 .IP " 1." 4
618 Discoverable Partitions Specification
619 .RS 4
620 \%https://uapi-group.org/specifications/specs/discoverable_partitions_specification
621 .RE
622 .IP " 2." 4
623 It is recommended for other tools to set and check
624 \fI$SUDO_UID\fR
625 as appropriate, treating it is a common interface.
626