[systemd-bugs] [Bug 86465] journal logs from service stdout/stderr split at 2048 chars

[bugzilla-daemon at freedesktop.org]

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

--- Comment #7 from Steve <s at ocado.com> ---
I got around this limitation/feature by creating a wrapper around the docker
container that sucks up stdout/stderr and sends it directly to the journald
socket.

While this works like a champ, it is not really an optimal solution, why do we
need to do a break at LINE_MAX? This is not consistent with the maximum log
line size and is not the behaviour that you would 'expect'.

Can we not just remove the LINE_MAX break code entirely?

-- 
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/20141215/746eb781/attachment.html>