From: John Fremlin <vii@users.sourceforge.net>
To: Dan Kegel <dank@kegel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: A signal fairy tale
Date: 28 Jun 2001 13:58:03 +0100 [thread overview]
Message-ID: <m23d8kiwx0.fsf@boreas.yi.org.> (raw)
In-Reply-To: <3B38860D.8E07353D@kegel.com>
In-Reply-To: <3B38860D.8E07353D@kegel.com> (Dan Kegel's message of "Tue, 26 Jun 2001 05:54:37 -0700")
Dan Kegel <dank@kegel.com> writes:
[...]
> A signal number cannot be opened more than once concurrently;
> sigopen() thus provides a way to avoid signal usage clashes
> in large programs.
Signals are a pretty dopey API anyway - so instead of trying to patch
them up, why not think of something better for AIO?
[...]
--
http://ape.n3.net
next prev parent reply other threads:[~2001-06-28 12:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-26 12:54 A signal fairy tale Dan Kegel
2001-06-27 3:56 ` Christopher Smith
2001-06-27 6:21 ` Balbir Singh
2001-06-27 18:11 ` Christopher Smith
2001-06-28 3:28 ` Balbir Singh
2001-06-27 9:18 ` Jamie Lokier
2001-06-27 18:16 ` Christopher Smith
2001-06-28 12:58 ` John Fremlin [this message]
2001-06-28 16:21 ` Jamie Lokier
2001-06-29 8:22 ` Christopher Smith
2001-06-29 11:47 ` John Fremlin
-- strict thread matches above, loose matches on Subject: below --
2001-06-28 2:49 Daniel R. Kegel
2001-06-29 8:18 ` Christopher Smith
2001-06-29 9:05 ` Dan Kegel
2001-06-28 2:57 Daniel R. Kegel
2001-06-29 8:19 ` Christopher Smith
2001-06-29 9:29 ` Dan Kegel
2001-06-29 18:46 ` Dan Kegel
2001-07-02 22:33 ` Christopher Smith
2001-06-28 3:04 Daniel R. Kegel
2001-06-28 14:46 ` Jamie Lokier
2001-06-28 20:11 Daniel R. Kegel
2001-06-29 8:31 ` Christopher Smith
[not found] <fa.d69j5vv.ej8irj@ifi.uio.no>
[not found] ` <fa.h2rpibv.87m5bp@ifi.uio.no>
2001-06-28 14:59 ` Dan Maas
2001-06-28 15:21 ` Alan Cox
2001-06-29 8:26 ` Christopher Smith
2001-06-29 11:56 ` Chris Wedgwood
2001-06-30 10:02 ` Jan Hudec
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=m23d8kiwx0.fsf@boreas.yi.org. \
--to=vii@users.sourceforge.net \
--cc=dank@kegel.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.