[systemd-bugs] [Bug 84923] writes to stdout (via journald) result in -EPIPE after systemd-journald.service restart

[bugzilla-daemon at freedesktop.org]

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

--- Comment #4 from Daniel Miranda <danielkza2 at gmail.com> ---
Please correct me if I'm spouting absolute nonsense, but I wonder if it would
be possible to fix this in journald with something like the following on
restart:

- journald: stop reading from the service output descriptors
- journald: start listening on a UNIX socket (lets call it the dump socket)
- journald: Spawn a secondary process which double forks
- aux: Connect to the dump socket, and start listening on a restore socket
- journald: pass the FDs over to the dump socket and possibly a serialized form
of state, close the FDs, then exit
- new journald: Check for the existence of the dump socket. If it exists, grab
back the state and the FDs, and signal the aux process to close
- new journald: Resume operating normally

-- 
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/20141130/fbff57ff/attachment.html>