Util-Linux package development
 help / color / mirror / Atom feed
From: Bernhard Voelker <mail@bernhard-voelker.de>
To: "Karel Zak" <kzak@redhat.com>, "Rüdiger Meier" <sweet_f_a@gmx.de>
Cc: util-linux@vger.kernel.org
Subject: Re: sfdisk, stderr/stdout output order
Date: Thu, 10 Mar 2016 15:08:28 +0100	[thread overview]
Message-ID: <56E17FDC.6010604@bernhard-voelker.de> (raw)
In-Reply-To: <20160310111605.n2jona662wvbgymh@ws.net.home>

On 03/10/2016 12:16 PM, Karel Zak wrote:
> On Thu, Mar 10, 2016 at 11:40:50AM +0100, Rüdiger Meier wrote:
>> I've found such test diffs with musl libc. Maybe it needs some fflush(3)
>> calls.
>
>   Yes, good point. I'll fix it.

I don't think you can enforce stdout/stderr to be synchronous.
Well, you can try with "stdbuf(1)", but only having coreutils >v7.5
(2009).  Why not check the output of both streams separately?

Have a nice day,
Berny

  reply	other threads:[~2016-03-10 14:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-10 10:40 sfdisk, stderr/stdout output order Rüdiger Meier
2016-03-10 11:16 ` Karel Zak
2016-03-10 14:08   ` Bernhard Voelker [this message]
2016-03-10 14:24     ` Karel Zak
2016-03-10 14:35       ` Rüdiger Meier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56E17FDC.6010604@bernhard-voelker.de \
    --to=mail@bernhard-voelker.de \
    --cc=kzak@redhat.com \
    --cc=sweet_f_a@gmx.de \
    --cc=util-linux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox