Re: error in server-running-p on M$

[Ulrich Mueller <ulm@kph.uni-mainz.de>]

>>>>> On Sat, 22 Nov 2008, Juanma Barranquero wrote:

>> Shouldn't it try to actually connect to the socket (in the
>> server-use-tcp case), to find out if the server is functional?
>> That would also be consistent with the behaviour for local sockets.

> The idea is to run a simple test, that does not have the risk of
> incurring in a timeout.

This doesn't catch all cases. For example, the server process could be
running on a remote machine, with the port tunnelled over ssh.

> Also, if the server authentication file says that Emacs process PID is
> using port P, and there's really an Emacs of pid PID but it is no
> longer answering to requests on port P, that is PID's problem, not the
> current instance's.

I think that the false positives are not the problem, but the false
negatives (i.e. port is in use, but server-running-p returns nil) are.

Ulrich