From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] signals Unix style?
Date: Fri, 14 Oct 2005 20:17:12 +0100 [thread overview]
Message-ID: <b84a0106d36823bd5ec2def90e0754d2@terzarima.net> (raw)
In-Reply-To: <Pine.GSO.4.61.0510141443250.25938@cps210.cps.cmich.edu.>
[-- Attachment #1: Type: text/plain, Size: 212 bytes --]
it's a string, so it's open-ended and largely up to the processes involved, but
see notify(2) for `a common set that includes ...' system messages.
"interrupt" and "alarm" are probably the most commonly used.
[-- Attachment #2: Type: message/rfc822, Size: 2618 bytes --]
From: ISHWAR RATTAN <rattan@cps.cmich.edu>
To: 9fans@cse.psu.edu
Subject: [9fans] signals Unix style?
Date: Fri, 14 Oct 2005 14:44:54 -0400 (EDT)
Message-ID: <Pine.GSO.4.61.0510141443250.25938@cps210.cps.cmich.edu.>
Is there a list of signals (Unix style) that can be
posted to or handled by a process?
-ishwar
prev parent reply other threads:[~2005-10-14 19:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-14 18:44 ISHWAR RATTAN
2005-10-14 19:17 ` Charles Forsyth [this message]
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=b84a0106d36823bd5ec2def90e0754d2@terzarima.net \
--to=forsyth@terzarima.net \
--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).