From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] What is required of an open file to be used in ape/select?
Date: Tue, 9 Apr 2002 10:23:44 -0400 [thread overview]
Message-ID: <5c6b9f52339d09f0f7245d66e3ed8693@plan9.bell-labs.com> (raw)
> I have a server in user space that I mount on /n/ed. It contains
> a file, /n/ed/cmsg. What behavior must /n/ed/cmsg have to be
> useful with ape/select? I wish to read when a control message arrives
> at the file.
I think that all files are equal in the eyes of ape select.
(Of course, it could be that select is broken and doesn't
work on any files. I assume you tried selecting on
/n/ed/cmsg and it didn't work.)
I'm not convinced you want to go down this path. It's
almost always easier to use libthread and have separate
procs reading from fds and passing data pointers back to a
main proc.
Russ
next reply other threads:[~2002-04-09 14:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 14:23 Russ Cox [this message]
2002-04-09 14:27 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2002-04-09 18:46 forsyth
2002-04-09 14:29 bwc
2002-04-09 14:28 Russ Cox
2002-04-09 14:18 bwc
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=5c6b9f52339d09f0f7245d66e3ed8693@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).