[systemd-bugs] [Bug 62650] systemd-coredump maintains the dump in memory

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=62650

Zbigniew Jedrzejewski-Szmek <zbyszek at in.waw.pl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #4 from Zbigniew Jedrzejewski-Szmek <zbyszek at in.waw.pl> ---
(In reply to comment #1)
> Should I expect some response?
When someone gets around to handling a bug, or they need some info, or have any
useful input at all, then yes. Otherwise, no.

(In reply to comment #3)
> All systemd-coredump instances exit correctly on their own when the dumps
> have been written to journal.
> 
> Not really a bug?
It's not a bug, things were working as designed. The problem was that writing
big entries to the journal was a bit slow.

As of http://cgit.freedesktop.org/systemd/systemd/commit/?id=34c10968,
coredumps are written to a file on disk. This should be both faster and require
less memory.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20140621/96783139/attachment.html>