<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - journal logs from service stdout/stderr split at 2048 chars" href="https://bugs.freedesktop.org/show_bug.cgi?id=86465#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - journal logs from service stdout/stderr split at 2048 chars" href="https://bugs.freedesktop.org/show_bug.cgi?id=86465">bug 86465</a> from <a class="email" href="mailto:s@ocado.com" title="Steve <s@ocado.com>"> Steve</a> <pre>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?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>