On Mon, 02 Feb 2004 21:30:19 +0100
Eric Marsden <[EMAIL PROTECTED]> wrote:
>
> >>>>> "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.
I get worse results, motifd cores when I start the debugger with out
starting motifd manually on localhost:
* (inspect *package*)
Starting server:
will_fork = False
will_trace = False
No Inet domain socket created.
path = /tmp/.motif_socket-p39548
Waiting for connection.
Accepting client on Unix socket.
Accepted client on fd 6
Server not forking.
greet_client: Unable to open display.
Bad file descriptor
Connection to server broken: Hit EOF while reading packet
Invoking debugger...
A Toolkit error has occurred.
Unable to connect to Motif server.
Restarts:
0: [ABORT] Return to Top-Level.
Debug (type H for help)
(INTERFACE::START-MOTIF-INSPECTOR
#<The COMMON-LISP-USER package, 15/21 internal, 0/9 external>)
Source: Error finding source:
Error in function DEBUG::GET-FILE-TOP-LEVEL-FORM: Source file no longer exists:
target:interface/inspect.lisp.
0]
Warning: Motif server died.
Status = :SIGNALED, exit code = 6.
and here is what I get in the window that gets syslog console
messages:
Feb 2 16:53:57 bogomips /kernel: pid 39548 (motifd), uid 1001: exited on signal 6
(core dumped)
But if I start it manually it works fine.
marc
>
> 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/>
>
