From: Zbigniew Jędrzejewski-Szmek Date: Fri, 23 Mar 2018 12:54:20 +0000 (+0100) Subject: man: add a note about "archived" journal files and when files can be copied X-Git-Tag: v239~477^2~3 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=4bb890bc04a6fd93e16eaafa72b0ad68c868a78c;p=thirdparty%2Fsystemd.git man: add a note about "archived" journal files and when files can be copied Issue #6673 requests advice on backup strategy. But the right backup strategy depends on many factors, too many to describe in a man page. So let's just provide some general information which files are mutable and that it is always safe to use/copy files. Closes #6673. --- diff --git a/man/systemd-journald.service.xml b/man/systemd-journald.service.xml index 8ca0e896abf..dfff107e1f1 100644 --- a/man/systemd-journald.service.xml +++ b/man/systemd-journald.service.xml @@ -261,9 +261,7 @@ systemd-tmpfiles --create --prefix /var/log/journal /etc/systemd/journald.conf - Configure - systemd-journald - behavior. See + Configure systemd-journald behavior. See journald.conf5. @@ -274,8 +272,7 @@ systemd-tmpfiles --create --prefix /var/log/journal /var/log/journal/machine-id/*.journal /var/log/journal/machine-id/*.journal~ - systemd-journald writes - entries to files in + systemd-journald writes entries to files in /run/log/journal/machine-id/ or /var/log/journal/machine-id/ @@ -287,7 +284,19 @@ systemd-tmpfiles --create --prefix /var/log/journal /var/log/journal is not available, or when is set in the journald.conf5 - configuration file. + configuration file. + + When systemd-journald ceases writing to a journal file, + it will be renamed to original-name@suffix.journal + (or original-name@suffix.journal~). + Such files are "archived" and will not be written to any more. + + In general, it is safe to read or copy any journal file (active or archived). + journalctl1 + and the functions in the + sd-journal3 + library should be able to read all entries that have been fully written. +