Hi, This has been discussion on IRC but I've not heard anything about it specifically nor have I seen any commits relating to it.
Using journald without persistent logs (i.e. /run only), I see the memory footprint of journald increasing over time. Checking the maps shows a very high count: [root@jimmy ~]# cat /proc/$(pidof systemd-journald)/maps | grep /run/log/journal/6cb2a4b2bd6df042e57da8a4000001d4/system.journal | wc -l 1641 Something is obviously not good there! journald is using something in the region of 250MB res. What's the best way to debug this? Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/ _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
