[Openmcl-devel] Running CCL as a daemon
dlw at itasoftware.com
Thu Feb 18 15:57:33 UTC 2010
Running ccl with --eval (-e) works fine.
Some things that you might consider doing, depending
on what behavior you want:
You might want to use --disable-debugger, which makes
ccl quit if there's an unhandled condition, rather than
enter the debugger, so that a monitoring program can
see that things have gone bad, and take action such
as restarting the daemon.
You might want to redirect stdout and stderr to files.
You might want to use the --no-init option to CCL to
avoid the loading of init files.
Inside Lisp, you might want to set up condition
handlers near the base of every process that
catch "all" signals (perhaps serious-condition).
This might, for example, log what happened,
perhaps including a stack trace, and restart
Ron Garret wrote:
> What's the right way to run CCL as a daemon? Do I have to build my own image with a custom initial function, or is there a way to do it with the regular CCL image and the -e or -l command line option?
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
More information about the Openmcl-devel