linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michał Nazarewicz" <m.nazarewicz@samsung.com>
To: Glynn Clements <glynn@gclements.plus.com>
Cc: Ardhan Madras <nightdecoder@gmail.com>,
	linux-c-programming@vger.kernel.org
Subject: Re: Help on pipe
Date: Mon, 13 Jul 2009 08:45:34 +0200	[thread overview]
Message-ID: <op.uwzud8p07p4s8u@amdc030.digital.local> (raw)
In-Reply-To: <19031.32022.804076.200185@cerise.gclements.plus.com>

>>>     waitpid(pid, &ret, 0);
>>>     close(fds[1]);

> Michał Nazarewicz wrote:
>> No need to close.

On Fri, 10 Jul 2009 19:40:38 +0200, Glynn Clements  
<glynn@gclements.plus.com> wrote:
> There definitely is a need to close, but it should be fclose(stream)
> *before* the waitpid(). As David points out, sort won't terminate
> until it has finished reading its input.

Yes, yes... David already pointed out the problem is with EOF not  
buffering.

-- 
Best regards,                                            _     _
  .o. | Liege of Serenly Enlightened Majesty of         o' \,=./ `o
  ..o | Computer Science,  Michał "mina86" Nazarewicz      (o o)
  ooo +-<m.nazarewicz@samsung.com>-<mina86@jabber.org>-ooO--(_)--Ooo--

--
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-07-13  6:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-10  6:22 Help on pipe Ardhan Madras
2009-07-10  7:06 ` Michał Nazarewicz
2009-07-10  7:34   ` Ardhan Madras
2009-07-10 17:40   ` Glynn Clements
2009-07-11  3:41     ` David Lee
2009-07-13  6:45     ` Michał Nazarewicz [this message]
2009-07-10  7:27 ` David Lee
  -- strict thread matches above, loose matches on Subject: below --
2009-07-10 18:21 Ardhan Madras

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=op.uwzud8p07p4s8u@amdc030.digital.local \
    --to=m.nazarewicz@samsung.com \
    --cc=glynn@gclements.plus.com \
    --cc=linux-c-programming@vger.kernel.org \
    --cc=nightdecoder@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).