From: lkv@isg.de
To: Christopher Friesen <cfriesen@nortelnetworks.com>
Cc: "Kernel, Linux" <linux-kernel@vger.kernel.org>
Subject: Re: Desperately missing a working "pselect()" or similar...
Date: Fri, 05 Oct 2001 18:40:29 +0200 [thread overview]
Message-ID: <3BBDE27D.2E65F818@isg.de> (raw)
In-Reply-To: <3BBDD37D.56D7B359@isg.de> <3BBDE1AA.98C4712F@nortelnetworks.com>
Christopher Friesen wrote:
> > I'm currently looking for a decent method to wait on either
> > an I/O event _or_ a signal coming from another process.
>
> > - Unix domain sockets would be awkward to use due to the fact
> > I'd need to come up with some "filenames" for them to bind to,
> > and both security considerations and the danger of "leaking"
> > files that remain on disk forever make me shudder...
>
> If you use a named socket in the abstract namespace, then it can't "leak" to
> disk....
Ok, but man 7 unix says:
SCM_CREDENTIALS and the abstract namespace were introduced with
Linux 2.2 and should not be used in portable programs
... and I really do want to write portable programs...
Regards,
Lutz Vieweg
--
Dipl. Phys. Lutz Vieweg | email: lkv@isg.de
Innovative Software AG | Phone/Fax: +49-69-505030 -120/-505
Feuerbachstrasse 26-32 | http://www.isg.de/people/lkv/
60325 Frankfurt am Main | ^^^ PGP key available here ^^^
next prev parent reply other threads:[~2001-10-05 16:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-05 15:36 Desperately missing a working "pselect()" or similar lkv
2001-10-05 16:19 ` Alexander Viro
2001-10-05 16:28 ` lkv
2001-10-05 16:36 ` Christopher Friesen
2001-10-05 16:40 ` lkv [this message]
2001-10-05 20:37 ` Bernd Eckenfels
2001-10-05 23:05 ` Alex Pennace
2001-10-05 23:13 ` Alan Cox
2001-10-05 23:52 ` Alex Pennace
2001-10-05 23:22 ` Neil Brown
2001-10-05 23:30 ` Alex Pennace
2001-10-05 23:43 ` David Schwartz
2001-10-06 0:03 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-10-08 16:32 lkv
2001-10-08 16:44 ` Alan Cox
2001-10-08 17:06 ` lkv
2001-10-08 17:24 ` Alan Cox
2001-10-09 13:37 ` Jan Hudec
2001-10-13 16:05 ` Jamie Lokier
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=3BBDE27D.2E65F818@isg.de \
--to=lkv@isg.de \
--cc=cfriesen@nortelnetworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.