shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2025-03-28 02:50:16 +03:00
Code

man: rework the discussion of Storage= a bit

Browse Source 
Most distributions default to persistent storage these days, hence don't
claim otherwise.
This commit is contained in:
Lennart Poettering 2017-11-02 11:33:01 +01:00
parent 131819424d
commit fc5f5706d3
1 changed files with 12 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
man/systemd-journald.service.xml
View File

@ -90,17 +90,19 @@
for more information about the collected metadata.
</para>
<para>Log data collected by the journal is primarily text-based
but can also include binary data where necessary. All objects
stored in the journal can be up to 2^64-1 bytes in size.</para>
<para>Log data collected by the journal is primarily text-based but can also include binary data where
necessary. Individual fields making up a log record stored in the journal may be up to 2^64-1 bytes in size.</para>
<para>By default, the journal stores log data in
<filename>/run/log/journal/</filename>. Since
<filename>/run/</filename> is volatile, log data is lost at
reboot. To make the data persistent, it is sufficient to create
<filename>/var/log/journal/</filename> where
<filename>systemd-journald</filename> will then store the
data:</para>
<para>The journal service stores log data either persistently below <filename>/var/log/journal</filename> or in a
volatile way below <filename>/run/log/journal/</filename> (in the latter case it is lost at reboot). By default, log
data is stored persistently if <filename>/var/log/journal/</filename> exists during boot, with an implicit fallback
to volatile storage otherwise. Use <varname>Storage=</varname> in
<citerefentry><refentrytitle>journald.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> to configure
where log data is placed, independently of the existence of <filename>/var/log/journal/</filename>.</para>
<para>On systems where <filename>/var/log/journal/</filename> does not exist yet but where persistent logging is
desired (and the default <filename>journald.conf</filename> is used), it is sufficient to create the directory, and
ensure it has the correct access modes and ownership:</para>
<programlisting>mkdir -p /var/log/journal
systemd-tmpfiles --create --prefix /var/log/journal</programlisting>