Quote:
> Yes you backgrounded it right, but when you exit a shell all child
> processes get sent a HUP signal(SIGHUP) because you hung up. And
> well behaved processes will exit. look at the nohup command for
> keeping lisp alive after you exit the shell, 'man nohup'
> marc
Thank you Marc for your help (I start to understand something...)
reading the content of nohup.out file it seems that when I exit the shell,
the lisp process receive an EOF every time it try to read from its standard
input. After 10 EOF it stops itself...
Maybe there is some options in executing cmucl to avoid this, but I didn't
see it.
Or maybe is not possible at all running that lisp as a demon....
Someone could say me if I have to change my way? My need is to interpret
some lisp code im my web application. Mod_lisp is perfect from my needs but
how can I deploy my application if I have to let a shell open on the
server?!
thanks,
Riccardo
here the content of nohup.out
------
* Help! 12 nested errors. KERNEL:*MAXIMUM-ERROR-DEPTH* exceeded.
Debug (type H for help)
(COMMON-LISP::DO-OUTPUT #<Stream for the Terminal> #.(SYSTEM:INT-SAP
#x402DC000)
Source:
*
Received EOF.
*
Received EOF.
*
Received EOF.
*
Received EOF.
*
Received EOF.
*
Received EOF.
*
Received EOF.
*
Received EOF.
*
Received EOF.
*
Received more than 10 EOFs; Aborting.