I have got a little further in diagnosing this "memory leak" of
systemd-journal. It appears to worsen when I have a process that emits
data to stdout. I presume that systemd-journal is attempting to put this
somewhere but failing, and consequently is buffering it in its own
process. Where is this logging supposed to go, and can I redirect it to
somewhere benign such as /dev/null?
Dave.
On 02/28/2012 02:51 PM, David Lambert wrote:
Please excuse if this is trivial, but I am a systemd newbie.
I am running systemd on Angstrom/Beaglebone. After a couple of days I
notice that the process systemd-journald had grown and was ultimately
killed by the kernel's OOM handler. I investigated the
systemd-journald.conf file which stated:
# See system-journald.conf(5) for details
I presume that this is a reference to a man page, but I have
downloaded systemd-43 and cannot find this documentation. I would
appreciate any links to this documentation and/or any suggestions as
to where the problem nay lie.
Best,
Dave.
_______________________________________________
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
_______________________________________________
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
