9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Lluís Batlle" <viriketo@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Pipes on UNIX
Date: Thu,  6 Sep 2007 22:40:21 +0200	[thread overview]
Message-ID: <45219fb00709061340t2f0f027ewd34ff976ef8392db@mail.gmail.com> (raw)
In-Reply-To: <4bddb19f76168d998a8085d9554d3b48@quanstro.net>

2007/9/6, erik quanstrom <quanstro@quanstro.net>:
> > Therefore, if I had a CGI similar to 'cat' (and I have), it would
> > deadlock due to the pipe_process2 not being read by apache if it gets
> > filled, the process blocks, and then pipe_process1 gets filled.
>
> no, you wouldn't.
>
> i believe the problem is the cgi and apache disagree on the termination
> condition.  make sure you close the fd 0 when you are done reading.
I used gdb, and my process doesn't reach at all the end of reading. It
gets blocked writting to stdout. The system input TCP queue to apache
is still filled with 70KB of data in the test I did. And the browser
didn't receive any byte. And I know my program processed an amount of
data (it makes the hard disk pain a bit, so I can 'hear' when it does
something).


  reply	other threads:[~2007-09-06 20:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-06 13:04 Lluís Batlle
2007-09-06 13:57 ` sqweek
2007-09-06 14:02   ` Lluís Batlle
2007-09-06 14:12     ` sqweek
2007-09-06 14:42       ` Lluís Batlle
2007-09-06 14:47         ` Gorka Guardiola
2007-09-06 14:57           ` Lluís Batlle
2007-09-06 15:52           ` ron minnich
2007-09-06 16:06             ` Gorka Guardiola
2007-09-06 20:17               ` Lluís Batlle
2007-09-06 20:33                 ` erik quanstrom
2007-09-06 20:40                   ` Lluís Batlle [this message]
2007-09-06 21:51                 ` Charles Forsyth
2007-09-06 14:04 ` Enrico Weigelt

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=45219fb00709061340t2f0f027ewd34ff976ef8392db@mail.gmail.com \
    --to=viriketo@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).