Re: terminating clisp: clisp.exe vs lisp.exe
"Pascal J. Bourguignon" <[email protected]>
| Newsgroups | gmane.lisp.clisp.devel |
|---|---|
| Organization | Informatimago |
| Message-ID | <[email protected]> |
Anton Vodonosov <[email protected]> writes: > Hello. > > My program starts clisp as a child process to do some work. > Sometimes this work may hang. > > In this case I would like to kill the child lisp process. > > clisp.exe starts another process, lisp.exe which, as I understand, > preforms all the job. > > It's not trivial to even get process id of lisp.exe. > > What are my options to reliable kill started CLISP? killall will kill ALL your clisp processes, not only the one you want to kill. Given the current state of affair, your best bet is to open a pipe between the parent process and the clisp process, and use it to provoke a killing sigchld > Is it possible to start CLISP in a way that it consists only of one process? You can also run lisp.exe directly. You must be careful with the options. Perhaps it would be a good idea to remove the call to fork() from the clisp driver? -- __Pascal Bourguignon__ http://www.informatimago.com/ A bad day in () is better than a good day in {}. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ clisp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/clisp-devel