Sat, Apr 20, 2024 at 16:45 Carl Edquist wrote:However, stdout
and stderr are still separate streams even if they refer to the same output
file/pipe/device, so partial lines are not interleaved in the order that they
were printed. will output abc\n123\n instead of
a1b2c3\n\n, even if
On Sat, 20 Apr 2024, Zachary Santer wrote:
This was actually in RHEL 7.
Oh. In that case it might be worth looking into ...
I don't know how buffering works when stdout and stderr get redirected
to the same pipe. You'd think, whatever it is, it would have to be smart
enough to keep them
On Sat, Apr 20, 2024 at 11:58 AM Carl Edquist wrote:
>
> On Thu, 18 Apr 2024, Zachary Santer wrote:
> >
> > Finally had a chance to try to build with 'stdbuf --output=L --error=L
> > --' in front of the build script, and it caused some crazy problems.
>
> For what it's worth, when I was trying
On Thu, 18 Apr 2024, Zachary Santer wrote:
On Wed, Mar 20, 2024 at 4:54 AM Carl Edquist wrote:
However, if stdbuf's magic env vars are exported in your shell (either
by doing a trick like 'export $(env -i stdbuf -oL env)', or else more
simply by first starting a new shell with 'stdbuf -oL
