> > > > Now that the operation of flush can be done automatically when you switch from Storage=volatile to #Storage=volatile, why do we still need journalctl --flush? > > > > To switch from volatile storage to persistent storage on boot as explained in the man page. On boot /var may not be available initially, so journald starts with /run and flush copies logs from /run to /var and switches to persistent storage. > So, can I assume that journalctl --flush is for Linux internal processes not for end users? -----邮件原件----- 发件人: systemd-devel <systemd-devel-bounces@xxxxxxxxxxxxxxxxxxxxx> 代表 systemd-devel-request@xxxxxxxxxxxxxxxxxxxxx 发送时间: 2021-09-22 20:00 收件人: systemd-devel@xxxxxxxxxxxxxxxxxxxxx 主题: systemd-devel Digest, Vol 137, Issue 26 Send systemd-devel mailing list submissions to systemd-devel@xxxxxxxxxxxxxxxxxxxxx To subscribe or unsubscribe via the World Wide Web, visit https://lists.freedesktop.org/mailman/listinfo/systemd-devel or, via email, send a message with subject or body 'help' to systemd-devel-request@xxxxxxxxxxxxxxxxxxxxx You can reach the person managing the list at systemd-devel-owner@xxxxxxxxxxxxxxxxxxxxx When replying, please edit your Subject line so it is more specific than "Re: Contents of systemd-devel digest..." Today's Topics: 1. Re: What are the use cases of journalctl --flush ? (Andrei Borzenkov) ---------------------------------------------------------------------- Message: 1 Date: Wed, 22 Sep 2021 12:33:35 +0300 From: Andrei Borzenkov <arvidjaar@xxxxxxxxx> To: SystemD Devel <systemd-devel@xxxxxxxxxxxxxxxxxxxxx> Subject: Re: What are the use cases of journalctl --flush ? Message-ID: <CAA91j0UCeXHFmFK3bNW15SfxfcAAPdQUu3iMxq-nXwE0zXp8Ug@xxxxxxxxxxxxxx> Content-Type: text/plain; charset="UTF-8" On Wed, Sep 22, 2021 at 9:27 AM <krave1986121@xxxxxxxxx> wrote: > > Now that the operation of flush can be done automatically when you switch from Storage=volatile to #Storage=volatile, why do we still need journalctl --flush? > To switch from volatile storage to persistent storage on boot as explained in the man page. On boot /var may not be available initially, so journald starts with /run and flush copies logs from /run to /var and switches to persistent storage. ------------------------------ Subject: Digest Footer _______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel ------------------------------ End of systemd-devel Digest, Vol 137, Issue 26 **********************************************