7:08:52splittistSitting in my London hotel room waiting for the conference call with folks in three cities that are not London. The glamorous life of the road warrior. I keep thinking I should make time to see Xof, but, of course, I can't 'make' time (even though I live near CERN...).
8:47:30hjudtis there a way to catch SIGTERM and SIGINT signals in sbcl? i've tried trivial-signal, but the examples provided do not work; e.g. sending INT only invokes the sbcl debugger but the signal handler does not run.
8:53:17no-defun-allowedafter some idea generation in #lispcafe, i present the magrathea anti-vulnerability scanner hunchentoot mixin
8:58:31jackdanielalso regrading graceful exit I think there may be a nice interface for adding exit-hooks
8:58:38jackdanielwithout playing catch with signal handling
9:10:55hjudtthanks. i have added a function to sb-ext:*exit-hooks*, which gets called. additionally setting sb-ext:*timeout* to a lower value than the default 60 also solves my problem that sbcl takes too long to shutdown.
9:11:20hjudtprobably my open slime/sly connection prevents an earlier shutdown?
9:15:59hjudthm. disconnecting slime before sending TERM doesn't seem to make a difference.