[systemd-devel] logging in RAM and journald configuration issue
lennart at poettering.net
Tue Apr 2 16:47:00 UTC 2019
On Di, 02.04.19 17:42, Dave Howorth (systemd at howorth.org.uk) wrote:
> On 2019-03-20 Lennart Poettering wrote:
> > On Mi, 20.03.19 18:08, Dave Howorth (systemd at howorth.org.uk) wrote:
> > >
> > > At present AFAICT the log2ram.service runs
> > > Before=systemd-journald.service and various other services, so I
> > > think that aspect is covered.
> > I am not sure what this service does, but if all you want to do is
> > make changes to /var/log/journal before journald writes there it
> > should be sufficient to order it before systemd-journal-flush.service
> > which is nowadays the clear boundary when journald starts writing to
> > /var.
> Sorry for the late reply, but I'm just trying to understand this
> better. Is systemd-journal-flush.service documented anywhere?
It just invokes "journalctl --flush" which is documented here:
Lennart Poettering, Berlin
More information about the systemd-devel