Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!jd
From: jd@csd4.milw.wisc.edu (James R Drinkwater)
Newsgroups: comp.unix.wizards
Subject: Signals after exec
Message-ID: <1187@csd4.milw.wisc.edu>
Date: 21 Feb 89 21:55:17 GMT
Sender: news@csd4.milw.wisc.edu
Reply-To: jd@csd4.milw.wisc.edu (James R Drinkwater)
Distribution: na
Organization: University of Wisconsin-Milwaukee
Lines: 13


Signals that are caught and assigned a signal handler are reset after
a call to exec.  Besides the fact that if they were not reset, a security
problem would result with set-uid programs that are exec'ed, the only other
reason I can think of is that exec overlays the calling process, so all
code is lost.  Are there other reasons that I am missing?  Can you think
of examples in which you would like to keep a signal handler installed
across exec?
--

Jim Drinkwater
Internet: jd@csd4.milw.wisc.edu
UUCP: uwvax!uwmcsd1!uwmcsd4!jd