Chris Baker <electro <at> 1939worldsfair.com> writes:
(...)
> > says that "CLM consists of three components: A CLM daemon, a CLM server,
and a
> > package of Common Lisp functions."
> >
> > All I could find was:
> >
> > /usr/lib/cmucl/subsystems/clm-library.x86f
> >
(...)
> > "Server not forking"
> > "Connection to server broken"
> > Then, ISLISP just chokes and dies...
>
Hi --
Thanks for answering.
I meant ILISP, not ISLISP (ISLISP is another one from the LISP family, by the
way).
> I have this problem intermittantly, but I've never been able to track
> down a reproducible case. It only happens when you get an error after
> clm is loaded but using the inspector.
>
Interesting. I guess the inspector did load (pretty emotional sighting,
actually, for me).
> To get this to work:
>
> 1. Make sure you aren't running any stray copies of motifd (the
> server process).
>
Do I simply do ./motidf ? How do I start this server?
> 2. Clean out any stray .motif* files in your /tmp directories.
>
Will these files be generated automagically in /tmp?
And what about the other variables, for instance, xtk::*default-binary* and
such in the CLM manual? Do you set them at all?
> Good luck.
>
Thanks, I'm gonna need it.
> HTH,
Sure does.
>
> cbb
>
Henry
