From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ulrich Mueller Newsgroups: gmane.emacs.devel Subject: Re: error in server-running-p on M$ Date: Sat, 22 Nov 2008 15:29:31 +0100 Message-ID: <18728.5963.672940.47287@a1ihome1.kph.uni-mainz.de> References: <18728.4982.765983.511070@a1ihome1.kph.uni-mainz.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1227364758 25038 80.91.229.12 (22 Nov 2008 14:39:18 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 22 Nov 2008 14:39:18 +0000 (UTC) Cc: Eli Zaretskii , emacs-devel@gnu.org To: "Juanma Barranquero" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Nov 22 15:40:20 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1L3ted-0000sn-PP for ged-emacs-devel@m.gmane.org; Sat, 22 Nov 2008 15:40:12 +0100 Original-Received: from localhost ([127.0.0.1]:49289 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L3tdU-0001qs-Ar for ged-emacs-devel@m.gmane.org; Sat, 22 Nov 2008 09:39:00 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1L3tXs-0007oY-FN for emacs-devel@gnu.org; Sat, 22 Nov 2008 09:33:12 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1L3tXq-0007o0-3d for emacs-devel@gnu.org; Sat, 22 Nov 2008 09:33:10 -0500 Original-Received: from [199.232.76.173] (port=37219 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L3tXp-0007nq-El for emacs-devel@gnu.org; Sat, 22 Nov 2008 09:33:09 -0500 Original-Received: from a1iwww1.kph.uni-mainz.de ([134.93.134.1]:47476) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1L3tUS-0005cu-GH; Sat, 22 Nov 2008 09:29:40 -0500 Original-Received: from a1ihome1.kph.uni-mainz.de (a1ihome1.kph.uni-mainz.de [134.93.134.75]) by a1iwww1.kph.uni-mainz.de (8.14.0/8.13.4) with ESMTP id mAMETVbq017345; Sat, 22 Nov 2008 15:29:31 +0100 Original-Received: from a1ihome1.kph.uni-mainz.de (localhost [127.0.0.1]) by a1ihome1.kph.uni-mainz.de (8.14.0/8.14.1) with ESMTP id mAMETVpR020192; Sat, 22 Nov 2008 15:29:31 +0100 Original-Received: (from ulm@localhost) by a1ihome1.kph.uni-mainz.de (8.14.0/8.14.0/Submit) id mAMETVKX020187; Sat, 22 Nov 2008 15:29:31 +0100 In-Reply-To: X-Mailer: VM 8.0.2-487 under Emacs 22.2.1 (i686-pc-linux-gnu) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 1) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:105955 Archived-At: >>>>> 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