[Openmcl-devel] Handling SIGTERM in applications

Max Rottenkolber max at mr.gy
Wed Oct 26 01:09:28 UTC 2016


D'oh. I meant SIGINT. SIGTERM works just fine. To reprodcuce:

(save-application
 "sigint-test"
 :toplevel-function (lambda () (loop do (sleep 1)))
 :error-handler :quit
 :purify t
 :prepend-kernel t)

$ ./sigint-test # send it SIGINT
  C-c C-c> Break: interrupt signal
> While executing: CCL::%NANOSLEEP, in process toplevel(2).
> Type :GO to continue, :POP to abort, :R for a list of available restarts.
> If continued: Return from BREAK.
> Type :? for other options.
1 >

(Note that there is no actual break loop, it just prints the above and gets
stuck, ignoring input, or a subsequent SIGINT.)


On Tue, 20 Sep 2016 12:00:54 +0000, Max Rottenkolber wrote:

> Hello everyone,
> 
> I build my application using SAVE-APPLICATION and it works fine, except that it
> enters the debugger on SIGTERM even though I supply “:error-handler :quit”.
> 
> I feel like this is a bug.
> 
> Be it a bug or not, is there currently a way to change the signal handler
> behavior? I need my application to be a good Unix citizen. :-)
> 
> Cheers,
> Max
> 
> 
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> https://lists.clozure.com/mailman/listinfo/openmcl-devel




More information about the Openmcl-devel mailing list