[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: emacsclient can't connect to socket

From: Stefan Monnier
Subject: Re: emacsclient can't connect to socket
Date: Tue, 29 Jul 2003 14:46:50 -0400

> "Stefan Monnier" <monnier+gnu/emacs/address@hidden> writes:
> >> stat64("/tmp/emacs1001-debian/server", 0xbfffd80c) = -1 ENOENT (No such
> >> file or directory)
> >
> > What's the relationship between `debian' (the hostname
> > that emacsclient used) and `5100784654140001' (the hostname that
> > server.el used) ?  It seems that the hostname used by server.el
> > is wrong.  What does M-: (system-name) RET return ?
> The big number was a part of my old FQDN, the new FQDN returned by
> (system-name) is "ID-97899.user.dfn.cis.de" and before you want to ask
> after my /etc/hosts i give it to you:
> Old line: debian 5100784654140001.dialin.t-online.de
> New line: debian ID-97899.user.dfn.cis.de
> But the error also occured before changing my FQDN

The problem is that elisp (in which server.el is written) only has
access to your FQDN, whereas emacsclient.c doesn't bother to try and
figure out an FQDN.

Since the socket is actually created in /tmp, I'm tempted to completely
get rid of the hostname there, so it'd just be /tmp/emacs1001/server,
so we'd get rid of the whole problem.

Does anybody see a problem with it ?
Could /tmp reasonably be shared between several machines ?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]