9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: sqweek <sqweek@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 21:57:24 +0800	[thread overview]
Message-ID: <140e7ec30709060657r72fbb10fjf118a72452a30a16@mail.gmail.com> (raw)
In-Reply-To: <45219fb00709060604s2d6fc50ex270cfcf30c36067a@mail.gmail.com>

On 9/6/07, Lluís Batlle <viriketo@gmail.com> wrote:
> Hello,
>
> I understand from [1] that named pipes are suposed to use the
> filesystem as an "unlimited" buffer for the pipe. This would be an
> advantage against a pipe deadlock I'm experiencing using unnamed pipes
> (a CGI communicating wit Apache), but I cannot reproduce the
> "unlimited buffer" in Linux.

 On linux you want fifo(7), which says "When processes are exchanging
data via the FIFO, the kernel passes  all  data  internally  without
writing it to the file system.". Should answer the rest of your
questions.
-sqweek

  reply	other threads:[~2007-09-06 13:57 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 [this message]
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
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=140e7ec30709060657r72fbb10fjf118a72452a30a16@mail.gmail.com \
    --to=sqweek@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).