Re: Sbcl-help Digest, Vol 207, Issue 10

On Fri, May 03, 2024 at 01:49:43AM -0400, steve gonedes wrote:
> 
> On 4/27/24 12:35 PM, [email protected] wrote:
> > Send Sbcl-help mailing list submissions to
> > 	[email protected]
> > 
> > To subscribe or unsubscribe via the World Wide Web, visit
> > 	https://lists.sourceforge.net/lists/listinfo/sbcl-help
> > or, via email, send a message with subject or body 'help' to
> > 	[email protected]
> > 
> > You can reach the person managing the list at
> > 	[email protected]
> > 
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of Sbcl-help digest..."
> > 
> > Today's Topics:
> > 
> >     1. Re: capturing system shutdown signals? (Jeff Cunningham)
> >     2. Re: capturing system shutdown signals? (Stas Boukarev)
> >     3. Re: capturing system shutdown signals? (Jeff Cunningham)
> > 
> 
> 
> short answer is no. man 7 signal
> 
> 
> The signals SIGKILL and SIGSTOP cannot be caught, blocked, or ignored.

I played around with some of that in a Tcl/Tk app 20+y ago. It turned
out that one could _kindof_ catch SIGSTOP, but only after the fact.
Observed behaviour:
 - install handler for SIGSTOP
 - send SIGSTOP to process
 - process gets suspended (as expected)
 - send SIGCONT, job resumes, previously set up SIGSTOP handler
   runs now

Not overly useful, but a fun corner case. Of course there is nothing
one can do for SIGKILL.

Kind regards,
           Alex.
-- 
"Opportunity is missed by most people because it is dressed in overalls and
 looks like work."                                      -- Thomas A. Edison