diff options
author | Lennart Poettering <lennart@poettering.net> | 2019-11-27 19:24:44 +0100 |
---|---|---|
committer | Lennart Poettering <lennart@poettering.net> | 2019-11-28 14:33:31 +0100 |
commit | 870a2d85d089f3373f6e46d392ddcf161622d39d (patch) | |
tree | 090ae254fcf0b86aaedda563caaeddcde4bc2d90 /man/systemd-journald.service.xml | |
parent | man: add reference to journald man page from systemd.journal-fields(7) (diff) | |
download | systemd-870a2d85d089f3373f6e46d392ddcf161622d39d.tar.xz systemd-870a2d85d089f3373f6e46d392ddcf161622d39d.zip |
man: don't claim journalctl would still use signals
It's using the varlink interface these days.
Diffstat (limited to 'man/systemd-journald.service.xml')
-rw-r--r-- | man/systemd-journald.service.xml | 32 |
1 files changed, 13 insertions, 19 deletions
diff --git a/man/systemd-journald.service.xml b/man/systemd-journald.service.xml index 8bbb9931cf..ea6fb54673 100644 --- a/man/systemd-journald.service.xml +++ b/man/systemd-journald.service.xml @@ -136,36 +136,30 @@ systemd-tmpfiles --create --prefix /var/log/journal</programlisting> <varlistentry> <term>SIGUSR1</term> - <listitem><para>Request that journal data from - <filename>/run/</filename> is flushed to - <filename>/var/</filename> in order to make it persistent (if - this is enabled). This must be used after - <filename>/var/</filename> is mounted, as otherwise log data - 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 + <listitem><para>Request that journal data from <filename>/run/</filename> is flushed to + <filename>/var/</filename> in order to make it persistent (if this is enabled). This must be used + after <filename>/var/</filename> is mounted, as otherwise log data from <filename>/run</filename> is + never flushed to <filename>/var</filename> regardless of the configuration. Use the + <command>journalctl --flush</command> command to request flushing of the journal files, and wait for the operation to complete. See - <citerefentry><refentrytitle>journalctl</refentrytitle><manvolnum>1</manvolnum></citerefentry> - for details.</para></listitem> + <citerefentry><refentrytitle>journalctl</refentrytitle><manvolnum>1</manvolnum></citerefentry> for + details.</para></listitem> </varlistentry> <varlistentry> <term>SIGUSR2</term> - <listitem><para>Request immediate rotation of the journal - files. The <command>journalctl --rotate</command> command uses - this signal to request journal file - rotation.</para></listitem> + <listitem><para>Request immediate rotation of the journal files. Use the <command>journalctl + --rotate</command> command to request journal file rotation, and wait for the operation to + complete.</para></listitem> </varlistentry> <varlistentry> <term>SIGRTMIN+1</term> - <listitem><para>Request that all unwritten log data is written - to disk. The <command>journalctl --sync</command> command uses - this signal to trigger journal synchronization, and then waits - for the operation to complete.</para></listitem> + <listitem><para>Request that all unwritten log data is written to disk. Use the <command>journalctl + --sync</command> command to trigger journal synchronization, and wait for the operation to + complete.</para></listitem> </varlistentry> </variablelist> </refsect1> |