Xref: utzoo comp.unix.questions:28766 comp.unix.internals:2078 comp.unix.wizards:24142
Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!fub!tmpmbx!scuzzy!src
From: src@scuzzy.in-berlin.de (Heiko Blume)
Newsgroups: comp.unix.questions,comp.unix.internals,comp.unix.wizards
Subject: Re: SIGCONT occurs after a SIGTERM
Message-ID: <1991Feb13.213110.1074@scuzzy.in-berlin.de>
Date: 13 Feb 91 21:31:10 GMT
References: <7103@fs1.cam.nist.gov> <richard.666333628@fafnir.la.locus.com>
Organization: Contributed Software
Lines: 14

richard@locus.com (Richard M. Mathews) writes:
>The solution is don't catch SIGCONT.  Your SIGTSTP handler knows when
>the program resumes anyway because the line after the "kill" which
>caused it to suspend itself will not be reached until the program is
>resumed.

which fails miserably when you get the uncatchable SIGSTOP.
*yes*, i do use SIGSTOP, there are programs that disable
the SIGTSTP feature, and i won't let those go unsuspended.
-- 
      Heiko Blume <-+-> src@scuzzy.in-berlin.de <-+-> (+49 30) 691 88 93
                    public source archive [HST V.42bis]:
        scuzzy Any ACU,f 38400 6919520 gin:--gin: nuucp sword: nuucp
                     uucp scuzzy!/src/README /your/home