1JOURNAL-REMOTE.CONF(5) journal-remote.conf JOURNAL-REMOTE.CONF(5)
2
6 journal-remote.conf, journal-remote.conf.d - Configuration files for
7 the service accepting remote journal uploads
8
10 /etc/systemd/journal-remote.conf
11 /etc/systemd/journal-remote.conf.d/*.conf
13 /run/systemd/journal-remote.conf.d/*.conf
15 /usr/lib/systemd/journal-remote.conf.d/*.conf
17
19 These files configure various parameters of systemd-journal-
20 remote.service(8). See systemd.syntax(7) for a general description of
21 the syntax.
22
24 The default configuration is set during compilation, so configuration
25 is only needed when it is necessary to deviate from those defaults.
26 Initially, the main configuration file in /etc/systemd/ contains
27 commented out entries showing the defaults as a guide to the
28 administrator. Local overrides can be created by editing this file or
29 by creating drop-ins, as described below. Using drop-ins for local
30 configuration is recommended over modifications to the main
31 configuration file.
32 In addition to the "main" configuration file, drop-in configuration
34 snippets are read from /usr/lib/systemd/*.conf.d/,
35 /usr/local/lib/systemd/*.conf.d/, and /etc/systemd/*.conf.d/. Those
36 drop-ins have higher precedence and override the main configuration
37 file. Files in the *.conf.d/ configuration subdirectories are sorted by
38 their filename in lexicographic order, regardless of in which of the
39 subdirectories they reside. When multiple files specify the same
40 option, for options which accept just a single value, the entry in the
41 file sorted last takes precedence, and for options which accept a list
42 of values, entries are collected as they occur in the sorted files.
43 When packages need to customize the configuration, they can install
45 drop-ins under /usr/. Files in /etc/ are reserved for the local
46 administrator, who may use this logic to override the configuration
47 files installed by vendor packages. Drop-ins have to be used to
48 override package drop-ins, since the main configuration file has lower
49 precedence. It is recommended to prefix all filenames in those
50 subdirectories with a two-digit number and a dash, to simplify the
51 ordering of the files.
52 To disable a configuration file supplied by the vendor, the recommended
54 way is to place a symlink to /dev/null in the configuration directory
55 in /etc/, with the same filename as the vendor configuration file.
56
58 All options are configured in the [Remote] section:
59 Seal=
61 Periodically sign the data in the journal using Forward Secure
62 Sealing.
63 SplitMode=
65 One of "host" or "none".
66 ServerKeyFile=
68 SSL key in PEM format.
69 ServerCertificateFile=
71 SSL certificate in PEM format.
72 TrustedCertificateFile=
74 SSL CA certificate.
75 MaxUse=, KeepFree=, MaxFileSize=, MaxFiles=
77 These are analogous to SystemMaxUse=, SystemKeepFree=,
78 SystemMaxFileSize= and SystemMaxFiles= in journald.conf(5).
79 MaxUse= controls how much disk space the systemd-journal-remote may
81 use up at most. KeepFree= controls how much disk space
82 systemd-journal-remote shall leave free for other uses.
83 systemd-journal-remote will respect both limits and use the smaller
84 of the two values.
85 MaxFiles= controls how many individual journal files to keep at
87 most. Note that only archived files are deleted to reduce the
88 number of files until this limit is reached; active files will stay
89 around. This means that, in effect, there might still be more
90 journal files around in total than this limit after a vacuuming
91 operation is complete.
92
94 journald.conf(5), systemd(1), systemd-journal-remote.service(8),
95 systemd-journald.service(8)
96systemd 254 JOURNAL-REMOTE.CONF(5)