Re: Help tracking down cause of Hunchentoot crashes

Andreas Franke via Sbcl-help <[email protected]> Sat, 12 Apr 2025 10:00:44 +0000
Newsgroups gmane.lisp.steel-bank.general
Message-ID <trinity-2888f7b7-880c-42cd-8658-a4783bd85d6d-1744452044513@trinity-msg-rest-gmx-gmx-live-6c784bf6f5-r8fkx>
Could you set it up to run in a way such that stdout and stderr
of the sbcl process are associated with an on-disk file?

> The only logs I am aware of that might be relevant are the message and
> access logs that Hunchentoot writes, and kern and syslog in
> /var/log/. The latter two show nothing interesting over the interval
> in which it most recently died. The last access log entry was days
> after the last message log entry. Is there another log I don't know
> about?