public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J . A . Magallon" <jamagallon@able.es>
To: "Miller, Brendan" <Brendan.Miller@Dialogic.com>
Cc: "'linux-kernel @ vger . kernel . org'" <linux-kernel@vger.kernel.org>
Subject: Re: bidirectional named pipe?
Date: Sat, 3 Feb 2001 01:47:11 +0100	[thread overview]
Message-ID: <20010203014711.A904@werewolf.able.es> (raw)
In-Reply-To: <EFC879D09684D211B9C20060972035B1D4684F@exchange2ca.sv.dialogic.com>
In-Reply-To: <EFC879D09684D211B9C20060972035B1D4684F@exchange2ca.sv.dialogic.com>; from Brendan.Miller@Dialogic.com on Sat, Feb 03, 2001 at 01:33:09 +0100

Perhaps man 2 mkfifo ?

On 02.03 "Miller, Brendan" wrote:
> 
> I've countless web searches and linux-kernel archives, but I haven't yet
> found the answer to my question.
> 
> I'm porting some software to Linux that requires use of a bidirectional,
> named pipe.  The architecture is as follows:  A server creates a named pipe
> in the /tmp directory.  Any client can then open("/tmp/pipename",
> O_RDWR|O_NDELAY) and gain access to the server.  The pipe is bidirectional,
> so the client and server communicate on the same pipe.  I support a number
> of clients on the single pipe using file-locking to prohibit from two
> clients from writing/reading at once.
> 
> How can I do this under Linux?  In SVR4 Unices, I just use pipe() as it's
> pipes are bidirectional, and I can attach a name with fattach().  In SVR3
> Unices, I go through a bunch of hacking using the "stream clone device --
> /dev/spx".  I experiemented with socket-based pipes under Linux, but I
> couldn't gain access to them by open()ing the name.  Is there help?  I
> really don't want to use LiS (the Linux Streams) package, as I'd rather do
> something native and not be dependent on another module.  Plus, I read
> somewhere that this was a poor way to do things.
> 
> Brendan
> 
> Please cc: me personally, as I am not subscribed.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
> 
-- 
J.A. Magallon                                                      $> cd pub
mailto:jamagallon@able.es                                          $> more beer

Linux werewolf 2.4.1-ac1 #2 SMP Fri Feb 2 00:19:04 CET 2001 i686

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-02-03  0:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-03  0:33 bidirectional named pipe? Miller, Brendan
2001-02-03  0:47 ` J . A . Magallon [this message]
2001-02-03  2:41 ` Wakko Warner
2001-02-03  7:51 ` Alan Cox
2001-02-03 14:28   ` Jamie Lokier
2001-02-07 23:09   ` David L. Nicol
2001-02-08 23:10     ` H. Peter Anvin
2001-02-10  5:12       ` Chris Wedgwood
2001-02-11  1:38         ` H. Peter Anvin
2001-02-10  0:31     ` David L. Nicol
2001-02-10  1:37       ` Doug McNaught
  -- strict thread matches above, loose matches on Subject: below --
2001-02-03  0:49 Miller, Brendan
2001-02-03  4:55 Miller, Brendan

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=20010203014711.A904@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=Brendan.Miller@Dialogic.com \
    --cc=linux-kernel@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