journal-remote.conf, journal-remote.conf.d — Configuration files for the service accepting remote journal uploads
The default configuration is set during compilation, so configuration is only needed when it is
necessary to deviate from those defaults. The main configuration file is either in
/etc/systemd/ and contains commented out
entries showing the defaults as a guide to the administrator. Local overrides can be created by creating
drop-ins, as described below. The main configuration file can also be edited for this purpose (or a copy
/etc/ if it's shipped in
/usr/) however using drop-ins for
local configuration is recommended over modifications to the main configuration file.
In addition to the "main" configuration file, drop-in configuration snippets are read from
/etc/systemd/*.conf.d/. Those drop-ins have higher precedence and override the
main configuration file. Files in the
*.conf.d/ configuration subdirectories are
sorted by their filename in lexicographic order, regardless of in which of the subdirectories they
reside. When multiple files specify the same option, for options which accept just a single value, the
entry in the file sorted last takes precedence, and for options which accept a list of values, entries
are collected as they occur in the sorted files.
When packages need to customize the configuration, they can install drop-ins under
/usr/. Files in
/etc/ are reserved for the local administrator,
who may use this logic to override the configuration files installed by vendor packages. Drop-ins have to
be used to override package drop-ins, since the main configuration file has lower precedence. It is
recommended to prefix all filenames in those subdirectories with a two-digit number and a dash, to
simplify the ordering of the files. This also defined a concept of drop-in priority to allow
distributions to ship drop-ins within a specific range lower than the range used by users. This should
lower the risk of package drop-ins overriding accidentally drop-ins defined by users.
To disable a configuration file supplied by the vendor, the recommended way is to place a symlink
/dev/null in the configuration directory in
/etc/, with the
same filename as the vendor configuration file.
All options are configured in the [Remote] section:
Periodically sign the data in the journal using Forward Secure Sealing.
One of "
host" or "
SSL key in PEM format.
SSL certificate in PEM format.
SSL CA certificate.
These are analogous to
MaxUse= controls how much disk space
the systemd-journal-remote may use up at most.
KeepFree= controls how much disk
space systemd-journal-remote shall leave free for other uses.
systemd-journal-remote will respect both limits
and use the smaller of the two values.
MaxFiles= controls how many
individual journal files to keep at most. Note that only
archived files are deleted to reduce the number of files until
this limit is reached; active files will stay around. This
means that, in effect, there might still be more journal files
around in total than this limit after a vacuuming operation is