From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] APE select() and awkward Python subprocess PIPEfitting
Date: Tue, 26 Feb 2013 11:01:46 -0600 [thread overview]
Message-ID: <4AFE9B6F-F3E2-46A0-A705-C80980C8D511@corpus-callosum.com> (raw)
In-Reply-To: <CAOw7k5jVCpBud91z4rJD0frYs-AYQGiFvAjL6fELto-UgUEZNA@mail.gmail.com>
On Feb 26, 2013, at 10:26 AM, Charles Forsyth <charles.forsyth@gmail.com> wrote:
>
> On 26 February 2013 16:20, Charles Forsyth <charles.forsyth@gmail.com> wrote:
> If APE's select does the same, it will be fine, without breaking Python's pipes.
>
> "it will be fine" -- I meant X11 will be fine, since it's relying on closing a file descriptor in
> one part of the program to cause EBADF in the select in another part, which will cause it
> to check connections. But, but, why doesn't it just ... ? Never mind, I don't think we need to work that out,
> just behave in the same way as Linux select.
Hopefully with enough time to recover for another meal.
Of course, if we're going the Linux route, we'll need to up FD_SETSIZE to at
least 1024, we're currently at 96. Seems that 1024 has become the default
these days.
http://www.freebsd.org/cgi/man.cgi?query=select&sektion=2&manpath=FreeBSD+9.1-RELEASE
http://svnweb.freebsd.org/base/stable/9/sys/sys/select.h?view=markup
http://fxr.watson.org/fxr/source/kern/sys_generic.c?v=FREEBSD91#L893
next prev parent reply other threads:[~2013-02-26 17:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 2:29 Jeff Sickel
2013-02-26 5:53 ` Jeff Sickel
2013-02-26 11:25 ` Yaroslav
2013-02-26 11:41 ` Charles Forsyth
2013-02-26 16:17 ` Jeff Sickel
2013-02-26 15:29 ` Jeff Sickel
2013-02-26 16:20 ` Charles Forsyth
2013-02-26 16:26 ` Charles Forsyth
2013-02-26 17:01 ` Jeff Sickel [this message]
2013-02-26 18:36 ` Charles Forsyth
2013-02-26 16:48 ` Anthony Sorace
2013-02-26 18:25 ` Jeff Sickel
2013-02-27 2:03 ` Federico G. Benavento
2013-02-27 15:03 ` Jeff Sickel
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=4AFE9B6F-F3E2-46A0-A705-C80980C8D511@corpus-callosum.com \
--to=jas@corpus-callosum.com \
--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).