9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Venkatesh Srinivas <me@acm.jhu.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Passing a file descriptor between processes
Date: Fri,  5 Nov 2010 08:16:30 -0400	[thread overview]
Message-ID: <AANLkTi=KTpWad2QCwp1fH2uyEq3NDVG3O2mLmMp2-592@mail.gmail.com> (raw)
In-Reply-To: <8f55d962591f55cf217f8070f78dfa3b@coraid.com>

[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]

On Fri, Nov 5, 2010 at 7:41 AM, erik quanstrom <quanstro@labs.coraid.com>wrote:

> On Fri Nov  5 07:36:42 EDT 2010, rogpeppe@gmail.com wrote:
> > see srv(3)
> > http://plan9.bell-labs.com/magic/man2html/3/srv
> >
> > On 5 November 2010 10:29, Kirill A. Shutemov <kirill@shutemov.name>
> wrote:
> > > One of the ugliest interface in Unix is passing a file descriptor
> between
> > > processes [1]. Does Plan9 provide any mechanism for it?
> > >
> > > [1]
> http://book.chinaunix.net/special/ebook/addisonWesley/APUE2/0201433079/ch17lev1sec4.html
>
> the op may have seen this: http://lwn.net/Articles/411845/
> —which i found hard to read because the author's changing
> definition of "unix".
>
> - erik
>
>
There was a discussion here a while ago about it too: search for 'sendfd on
native Plan 9' from december 2008. Start here:
http://9fans.net/archive/2008/12/515, follow till January 2009.

Currently, if your processes have a common parent, you can use rfork; if
not, you must resort to #s. '#s' is a pretty unfortunate interface,
though...

-- vs

[-- Attachment #2: Type: text/html, Size: 1938 bytes --]

  reply	other threads:[~2010-11-05 12:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-05 10:29 Kirill A. Shutemov
2010-11-05 10:57 ` Lucio De Re
2010-11-05 10:58 ` erik quanstrom
2010-11-05 11:03 ` roger peppe
2010-11-05 11:41   ` erik quanstrom
2010-11-05 12:16     ` Venkatesh Srinivas [this message]
2010-11-05 12:21       ` erik quanstrom
2010-11-05 21:40         ` Skip Tavakkolian
2010-11-05 12:27       ` Lucio De Re

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='AANLkTi=KTpWad2QCwp1fH2uyEq3NDVG3O2mLmMp2-592@mail.gmail.com' \
    --to=me@acm.jhu.edu \
    --cc=9fans@9fans.net \
    /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).