>>>>> "fn" == Faried Nawaz <[EMAIL PROTECTED]> writes:
fn> Starting server:
fn> will_fork = False
fn> will_trace = False
fn> No Inet domain socket created.
fn> path = /tmp/.motif_socket-p906
fn>
fn> A Toolkit error has occurred.
fn> Unable to connect to Motif server.
CMUCL is defaulting to using a unix-domain socket to talk to the
motifd, but it seems that it can't connect to the socket.
fn> ps at this point shows me a running motifd:
fn>
fn> 915 p1 S 0:00.01 library:motifd -nofork -local (motifd)
this is strange: CMUCL is trying to speak to a motifd with pid 906,
whereas your motifd has pid 915. 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.
fn> If I start motifd as a separate process and eval
fn>
fn> (setf toolkit::*default-server-host* "localhost")
fn>
fn> I get the debugger panes to come up just fine.
there are two differences with this mode: it uses a TCP/IP connection
to the motifd, and the motifd process isn't a child of the lisp process.
BTW, the motifd should really be creating the unix-domain socket in a
700-mode user-owned directory in /tmp, for security reasons.
--
Eric Marsden <URL:http://www.laas.fr/~emarsden/>
