Eric Marsden wrote:
this is strange: CMUCL is trying to speak to a motifd with pid 906,
whereas your motifd has pid 915.
I'm not sure what happened then, but I ran it again, and yes, motifd is
lisp's child process:
% ps alx |grep 700
500 700 315 0 2 0 1299056 25208 select S+ p4 0:00.19 lisp
500 701 700 1 2 0 2912 472 poll I p4 0:00.01 library:moti
%
Can you check that that motifd is
really a child of your lisp process, and look at what unix-domain
sockets it has open ("lsof" will tell you this). Check that is has a
socket named "/tmp/.motif_socket-p<pid>" open. Then from CMUCL, try to
connect to that socket using EXT:CONNECT-TO-UNIX-SOCKET.
Right now I see
% lisp
CMU Common Lisp 18e, running on xpf.nilpotent.org
With core: /usr/local/lib/cmucl/lib/lisp.core
Dumped on: Mon, 2004-02-02 20:11:17+05:00 on xpf.nilpotent.org
See <http://www.cons.org/cmucl/> for support information.
Loaded subsystems:
Python 1.1, target Intel x86
CLOS 18e (based on PCL September 16 92 PCL (f))
Gray Streams Protocol Support
CLX X Library MIT R5.02
Motif toolkit and graphical debugger 1.0
* (setf foo bar)
Warning: Declaring FOO special.
Invoking debugger...
Starting server:
will_fork = False
will_trace = False
No Inet domain socket created.
path = /tmp/.motif_socket-p701
A Toolkit error has occurred.
Unable to connect to Motif server.
Restarts:
0: [ABORT] Return to Top-Level.
Debug (type H for help)
(EVAL BAR)
Source: Error finding source:
Error in function DEBUG::GET-FILE-TOP-LEVEL-FORM: Source file no longer exists:
target:code/eval.lisp.
0] Waiting for connection.
and
% sockstat |grep motif
fn motifd 701 5 stream /tmp/.motif_socket-p701
%
So it is an open unix socket. I can connect to it:
* (ext:connect-to-unix-socket "/tmp/.motif_socket-p701")
5
* Accepting client on Unix socket.
Accepted client on fd 6
Server not forking.
Faried.
--
The Great GNU has arrived, infidels, behold his wrath !
The dead are on their way to nowhere.
