[Openmcl-devel] Running CCL as a daemon
john at mcaleely.com
Fri Feb 19 01:13:45 UTC 2010
I thought I used -e and screen, but it turns out my production servers use:
screen -d -m -S tb-web \
ccl64 -l ~/tb_html/sites.lisp
So I'm guessing loading that lisp file starts things going. This is then wrapped in debian's start-stop-deamon infrastructure. (I develop on mac os, but deploy on debian).
I found detachtty picky to set up, and seemed suited to an app that treated stdout as a logging method. I prefer to direct logs elsewhere, and reserve the 'screen' session for interactive use of the REPL. I treated the presence of stdin/stdout/the REPL as mandatory features of lisp that I needed to support in my daemon, particularly given my newbie status with Lisp.
Is it the case that any setup that tries to close stdin, etc handles would need to also replace the REPL? (ie the initial idea of a custom initial function). I can see how that might be a neat solution, so I'd be interested in any details anyone has.
More information about the Openmcl-devel