Your company here โ€” click to reach over 10,000 unique daily visitors

journal-remote.conf - Man Page

Configuration files for the service accepting remote journal uploads




These files configure various parameters of systemd-journal-remote.service(8). See systemd.syntax(7) for a general description of the syntax.

Configuration Directories and Precedence

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 loaded from one of the listed directories in order of priority, only the first file found is used: /etc/systemd/, /run/systemd/, /usr/local/lib/systemd/ [1], /usr/lib/systemd/. The vendor version of the file contains commented out entries showing the defaults as a guide to the administrator. Local overrides can also be created by creating drop-ins, as described below. The main configuration file can also be edited for this purpose (or a copy in /etc/ if it's shipped under /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 /usr/lib/systemd/*.conf.d/, /usr/local/lib/systemd/*.conf.d/, and /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. This also defines a concept of drop-in priorities to allow OS vendors 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. It is recommended to use the range 10-40 for drop-ins in /usr/ and the range 60-90 for drop-ins in /etc/ and /run/, to make sure that local and transient drop-ins take priority over drop-ins shipped by the OS vendor.

To disable a configuration file supplied by the vendor, the recommended way is to place a symlink to /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.

Added in version 229.


One of "host" or "none".

Added in version 220.


SSL key in PEM format.

Added in version 220.


SSL certificate in PEM format.

Added in version 220.


SSL CA certificate.

Added in version 220.

MaxUse=, KeepFree=, MaxFileSize=, MaxFiles=

These are analogous to SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize= and SystemMaxFiles= in journald.conf(5).

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 complete.

Added in version 253.

See Also

journald.conf(5), systemd(1), systemd-journal-remote.service(8), systemd-journald.service(8)



๐Ÿ’ฃ๐Ÿ’ฅ๐Ÿงจ๐Ÿ’ฅ๐Ÿ’ฅ๐Ÿ’ฃ Please note that those configuration files must be available at all times. If /usr/local/ is a separate partition, it may not be available during early boot, and must not be used for configuration.

Referenced By

systemd.directives(7), systemd.index(7), systemd-journal-remote.service(8), systemd.syntax(7).

The man page journal-remote.conf.d(5) is an alias of journal-remote.conf(5).

systemd 256.2