delorie.com/archives/browse.cgi | search |
Date: | Wed, 3 Feb 1999 13:09:29 +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: Clarification re: signals |
In-Reply-To: | <3.0.6.32.19990202112714.008bf210@pop.netaddress.com> |
Message-ID: | <Pine.SUN.3.91.990203130909.29547F-100000@is> |
MIME-Version: | 1.0 |
Reply-To: | djgpp AT delorie DOT com |
On Tue, 2 Feb 1999, Paul Derbyshire wrote: > >No, SIGKILL is the only signal a process can't catch, so it's the > >"kill of last resort" to try to end a process. SIGKILL can only be > >sent, not trapped. The kill() function can send *any* signal to a > >process. > > A parent can use WIFSIGNALED and WTERMSIG to spot a SIGKILL kill of a child > though right? Yes.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |