Util-Linux package development
 help / color / mirror / Atom feed
From: J William Piggott <elseifthen@gmx.com>
To: Alexey Galakhov <agalakhov@gmail.com>
Cc: Karel Zak <kzak@redhat.com>, util-linux@vger.kernel.org
Subject: Re: [PATCH] hwclock: flush stdout in hwclock -c
Date: Tue, 28 Apr 2015 07:27:03 -0400	[thread overview]
Message-ID: <553F6E87.8030303@gmx.com> (raw)
In-Reply-To: <20150427234218.587e5435.agalakhov@gmail.com>



On 04/27/2015 05:42 PM, Alexey Galakhov wrote:
> On Mon, 27 Apr 2015 17:27:07 -0400
> J William Piggott <elseifthen@gmx.com> wrote:
> 
>> I do not understand what this patch accomplishes. stdout is line
>> buffered. All of hwclock -c output ends with \n, which flushes
>> the buffer. Then we flush it again with fflush? What am I missing?
> 
> stdout is line buffered only if it is not redirected.

Thanks for the explanation, I wasn't aware of that.

> Using the pipe
> symbol in shell to redirect the output i.e. to awk results in not
> flushing the buffer until it's full.
> 
> A quick test:
> $ hwclock -c | cat
> 
> 
> Regards,
> Alexey
> 

      parent reply	other threads:[~2015-04-28 11:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-16 15:26 [PATCH] hwclock: flush stdout in hwclock -c Alexey Galakhov
2015-04-20  0:34 ` J William Piggott
2015-04-20  7:28   ` Alexey Galakhov
2015-04-21 15:19     ` J William Piggott
2015-04-21 15:50       ` Alexey Galakhov
2015-04-21 19:12         ` J William Piggott
2015-04-27  8:27 ` Karel Zak
2015-04-27 21:27   ` J William Piggott
2015-04-27 21:42     ` Alexey Galakhov
2015-04-28  6:50       ` Bernhard Voelker
2015-04-28 11:27       ` J William Piggott [this message]

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=553F6E87.8030303@gmx.com \
    --to=elseifthen@gmx.com \
    --cc=agalakhov@gmail.com \
    --cc=kzak@redhat.com \
    --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