On 3/6/12 2:54 AM, Lennart Poettering wrote:
On Mon, 20.02.12 23:35, Olav Vitters (o...@vitters.nl) wrote:On Thu, Feb 09, 2012 at 08:12:55PM +0100, Lennart Poettering wrote:Now, of course, the journal shouldn't crash in the first place. This bug is still something to fix, but so far nobody managed to get me a bt of this. if the journal itself crashes a coredump will be placed in /var/lib/systemd/coredump/. It would be great if somebody could generate a backtrace of that!See https://bugs.mageia.org/show_bug.cgi?id=4588 and the duplicate for a few different stracktraces. Mageia still has v40 atm, so every crash is *very* noticeable.OK, so I looked and looked and looked at the code, and I think I finally figured it out now. Should be fixed in git, in 48496df. Please test! If I fixed the right bug then you should have encountered your problem only if the journal files grow quite large. Thanks for providing the stacktrace, much appreciated. Lennart
Lennart, Thx for keeping eye on this issue. I applied this commit over r43 and now sys is under stress tests. Next day I will report how it goes. Thx again for Your outstanding contribution to Linux world ! .br
<<attachment: warpme.vcf>>
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
