mirror of
https://github.com/systemd/systemd-stable.git
synced 2025-02-03 13:47:04 +03:00
man: don't claim journalctl would still use signals
It's using the varlink interface these days.
This commit is contained in:
parent
5a5bd9f7e0
commit
870a2d85d0
@ -136,36 +136,30 @@ systemd-tmpfiles --create --prefix /var/log/journal</programlisting>
|
|||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term>SIGUSR1</term>
|
<term>SIGUSR1</term>
|
||||||
|
|
||||||
<listitem><para>Request that journal data from
|
<listitem><para>Request that journal data from <filename>/run/</filename> is flushed to
|
||||||
<filename>/run/</filename> is flushed to
|
<filename>/var/</filename> in order to make it persistent (if this is enabled). This must be used
|
||||||
<filename>/var/</filename> in order to make it persistent (if
|
after <filename>/var/</filename> is mounted, as otherwise log data from <filename>/run</filename> is
|
||||||
this is enabled). This must be used after
|
never flushed to <filename>/var</filename> regardless of the configuration. Use the
|
||||||
<filename>/var/</filename> is mounted, as otherwise log data
|
<command>journalctl --flush</command> command to request flushing of the journal files, and wait for
|
||||||
from <filename>/run</filename> is never flushed to
|
|
||||||
<filename>/var</filename> regardless of the configuration. The
|
|
||||||
<command>journalctl --flush</command> command uses this signal
|
|
||||||
to request flushing of the journal files, and then waits for
|
|
||||||
the operation to complete. See
|
the operation to complete. See
|
||||||
<citerefentry><refentrytitle>journalctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>
|
<citerefentry><refentrytitle>journalctl</refentrytitle><manvolnum>1</manvolnum></citerefentry> for
|
||||||
for details.</para></listitem>
|
details.</para></listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term>SIGUSR2</term>
|
<term>SIGUSR2</term>
|
||||||
|
|
||||||
<listitem><para>Request immediate rotation of the journal
|
<listitem><para>Request immediate rotation of the journal files. Use the <command>journalctl
|
||||||
files. The <command>journalctl --rotate</command> command uses
|
--rotate</command> command to request journal file rotation, and wait for the operation to
|
||||||
this signal to request journal file
|
complete.</para></listitem>
|
||||||
rotation.</para></listitem>
|
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term>SIGRTMIN+1</term>
|
<term>SIGRTMIN+1</term>
|
||||||
|
|
||||||
<listitem><para>Request that all unwritten log data is written
|
<listitem><para>Request that all unwritten log data is written to disk. Use the <command>journalctl
|
||||||
to disk. The <command>journalctl --sync</command> command uses
|
--sync</command> command to trigger journal synchronization, and wait for the operation to
|
||||||
this signal to trigger journal synchronization, and then waits
|
complete.</para></listitem>
|
||||||
for the operation to complete.</para></listitem>
|
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
</variablelist>
|
</variablelist>
|
||||||
</refsect1>
|
</refsect1>
|
||||||
|
Loading…
x
Reference in New Issue
Block a user