From: dave@horsfall.org (Dave Horsfall)
Subject: [TUHS] Re {TUHS} Synchronous vs Asynchronous IO in Unix
Date: Sat, 26 Sep 2015 08:05:42 +1000 (EST) [thread overview]
Message-ID: <alpine.BSF.2.11.1509260755080.44325@aneurin.horsfall.org> (raw)
In-Reply-To: <201509211402.t8LE2E4K016401@coolidge.cs.Dartmouth.EDU>
On Mon, 21 Sep 2015, Doug McIlroy wrote:
> Signal() was there first and foremost to support SIGKILL; it did not
> purport to provide a sound basis for asynchronous IPC.
Yeah, brother. In a previous life, I got burned very badly when I relied
upon signals Doing the Right Thing [tm].
I think it was dump/restor, on a BSDi box; the damned thing communicated
betwixt its child processes with signals, and I lost every backup tape
without realising it.
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn!
next prev parent reply other threads:[~2015-09-25 22:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 14:02 Doug McIlroy
2015-09-25 17:08 ` Dan Cross
2015-09-25 22:05 ` Dave Horsfall [this message]
2015-09-25 23:16 ` Clem Cole
2015-09-25 23:23 ` Larry McVoy
2015-09-26 12:09 ` Dave Horsfall
2015-09-26 16:39 ` John Cowan
2015-09-27 7:19 ` Ramakrishnan Muthukrishnan
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=alpine.BSF.2.11.1509260755080.44325@aneurin.horsfall.org \
--to=dave@horsfall.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 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).