[systemd-devel] systemd-journalctl Failed to iterate through journal: Cannot allocate memory

[Lennart Poettering]

On Fri, 30.03.12 11:55, David Lambert (dave at lambsys.com) wrote:

> Lennart,
>     I think I found another clue. I noticed that the directory
> /var/log/journal was being used in addition to /var/run/log/journal.
> I do not want persistent logging, so I removed /var/log/journal.
> When I did this, systemd-journalctl appeared to work correctly.
>     Obviously I am mis-understanding (and mis-using) the journaling
> features of systemd. Could you please point me to any overview of
> where and how the journaling  sub-system stores its data?

/var/run is simply an alias for /run on modern systems.

If you reduce the number of journal files you are unlikely to hit the
address space limit, as described in the earlier mail.

It's documented in systemd-journald.conf(5).

Lennart

-- 
Lennart Poettering - Red Hat, Inc.