From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Passing a file descriptor between processes
Date: Fri, 5 Nov 2010 08:21:37 -0400 [thread overview]
Message-ID: <d62e1b7fa9afbb3f79f2552ec96a4bbd@brasstown.quanstro.net> (raw)
In-Reply-To: <AANLkTi=KTpWad2QCwp1fH2uyEq3NDVG3O2mLmMp2-592@mail.gmail.com>
> 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...
okay, practicially speaking, what's wrong with #s, and what do you propose?
- erik
next prev parent reply other threads:[~2010-11-05 12:21 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
2010-11-05 12:21 ` erik quanstrom [this message]
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=d62e1b7fa9afbb3f79f2552ec96a4bbd@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--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).