Date:	Wed, 3 Feb 1999 13:40:06 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Paul Derbyshire <pderbysh AT usa DOT net>
cc:	djgpp AT delorie DOT com
Subject:	Re: [Semi-OT] Call for collecting signal info.
In-Reply-To:	<3.0.6.32.19990202155352.0090cbd0@pop.netaddress.com>
Message-ID:	<Pine.SUN.3.91.990203133918.29547d-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com

On Tue, 2 Feb 1999, Paul Derbyshire wrote:

> 2. If you have seen on some system a signal macro defined that is
>    not mentioned in what you read in part 1, post a follow up
>    that does the following:
>    a. Includes this text without deleting it.
>    b. Snips anything else, like other peoples' signal info.
>    c. Adds for each macro they can contribute:
>       i.  The signal macro.
>       ii. The purpose of the signal.

From the nearest *nix box:

   SIGHUP   -- hangup (a remote terminal broke connection)
   SIGTRAP  -- single-step or debug instruction trap
   SIGEMT   -- emulator trap
   SIGSYS   -- bad argument to a system call
   SIGPIPE  -- write to a pipe with no one to read it
   SIGURG   -- urgent condition present on socket
   SIGSTOP  -- stop (cannot be blocked, caught, or ignored)
   SIGTSTP  -- stop signal from keyboard (by pressing Ctrl-Z)
   SIGCONT  -- continue after stop
   SIGCHLD  -- child process status (run, exit) has changed
   SIGTTIN  -- background read attempted from control terminal
   SIGTTOU  -- ditto, for write
   SIGIO    -- I/O is possible on a descriptor which requested this signal
   SIGXCPU  -- CPU time quota exceeded
   SIGXFSZ  -- file size quota exceeded
   SIGVTALRM-- virtual timer alarm
   SIGPROF  -- profiling timer alarm
   SIGWINCH -- window size/position changed
   SIGLOST  -- resource lost
   SIGUSR1  -- user-defined signal 1
   SIGUSR2  -- user-defined signal 2

- Raw text -