diff options
| author | Lennart Poettering <lennart@poettering.net> | 2012-10-16 22:58:07 +0200 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2012-10-16 22:58:07 +0200 |
| commit | fb0951b02ebf51a93acf12721d8857d31ce57ba3 (patch) | |
| tree | b9dd7a414d8a5a600d4b41e8e830faef7b6cf22a /man | |
| parent | 1f2da9ec5152cbf48c214969e079d9281ef68660 (diff) | |
journal: implement time-based rotation/vacuuming
This also enables time-based rotation (but not vacuuming) after 1month,
so that not more one month of journal is lost at a time per vacuuming.
Diffstat (limited to 'man')
| -rw-r--r-- | man/journald.conf.xml | 51 |
1 files changed, 51 insertions, 0 deletions
diff --git a/man/journald.conf.xml b/man/journald.conf.xml index b06a23d80e..66189bd92d 100644 --- a/man/journald.conf.xml +++ b/man/journald.conf.xml @@ -279,6 +279,57 @@ </varlistentry> <varlistentry> + <term><varname>MaxFileSec=</varname></term> + + <listitem><para>The maximum time to + store entries in a single journal + file, before rotating to the next + one. Normally time-based rotation + should not be required as size-based + rotation with options such as + <varname>SystemMaxFileSize=</varname> + should be sufficient to ensure that + journal files don't grow without + bounds. However, to ensure that not + too much data is lost at once when old + journal files are deleted it might + make sense to change this value from + the default of one month. Set to 0 to + turn off this feature. This setting + takes time values which may be + suffixed with the units year, month, + week, day, h, m to override the + default time unit of + seconds.</para></listitem> + </varlistentry> + + <varlistentry> + <term><varname>MaxRetentionSec=</varname></term> + + <listitem><para>The maximum time to + store journal entries for. This + controls whether journal files + containing entries older then the + specified time span are + deleted. Normally time-based deletion + of old journal files should not be + required as size-based deletion with + options such as + <varname>SystemMaxUse=</varname> + should be sufficient to ensure that + journal files don't grow without + bounds. However, to enforce data + retention policies it might make sense + to set change this value from the + default of 0 (which turns off this + feature). This settings also takes + time values which may be suffixed with + the units year, month, week, day, h, m + to override the default time unit of + seconds. </para></listitem> + </varlistentry> + + <varlistentry> <term><varname>ForwardToSyslog=</varname></term> <term><varname>ForwardToKMsg=</varname></term> <term><varname>ForwardToConsole=</varname></term> |