From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Juanma Barranquero" Newsgroups: gmane.emacs.devel Subject: Re: error in server-running-p on M$ Date: Sun, 23 Nov 2008 04:59:10 +0100 Message-ID: References: <18728.4982.765983.511070@a1ihome1.kph.uni-mainz.de> <18728.5963.672940.47287@a1ihome1.kph.uni-mainz.de> <18728.9899.815004.638335@a1ihome1.kph.uni-mainz.de> <18728.14527.648410.433140@a1ihome1.kph.uni-mainz.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1227412769 12313 80.91.229.12 (23 Nov 2008 03:59:29 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 23 Nov 2008 03:59:29 +0000 (UTC) Cc: Eli Zaretskii , Ulrich Mueller , emacs-devel@gnu.org To: dhruva Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Nov 23 05:00:32 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 1L4696-0005VA-Kw for ged-emacs-devel@m.gmane.org; Sun, 23 Nov 2008 05:00:28 +0100 Original-Received: from localhost ([127.0.0.1]:36524 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L467x-0008UA-D5 for ged-emacs-devel@m.gmane.org; Sat, 22 Nov 2008 22:59:17 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1L467s-0008RR-Hb for emacs-devel@gnu.org; Sat, 22 Nov 2008 22:59:12 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1L467s-0008Qx-20 for emacs-devel@gnu.org; Sat, 22 Nov 2008 22:59:12 -0500 Original-Received: from [199.232.76.173] (port=51099 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L467r-0008Qu-Tc for emacs-devel@gnu.org; Sat, 22 Nov 2008 22:59:11 -0500 Original-Received: from yw-out-1718.google.com ([74.125.46.158]:58497) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1L467r-0002WQ-Iu for emacs-devel@gnu.org; Sat, 22 Nov 2008 22:59:11 -0500 Original-Received: by yw-out-1718.google.com with SMTP id 9so710564ywk.66 for ; Sat, 22 Nov 2008 19:59:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=qAhbGXnW80Cfmt5tsaN93SJiHlrfHoRLP3hH3rRXL6E=; b=La1wpaJ0ZOdJUpIsqL4S7p3RneP2z5JObq6yU/seSbTB2XXZVj9n//FurLPRUl3b+z 01D9KINBhOWpAXa25uG2Zh+9UMx+ElG8LpHMQZrIfp0Wk5SIQeQ+ZuIW6FUAIsVP7WF7 XZkVf0RxXroJbXdG/Y3eO13fcS0/TAKFPCKzI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=Xtr7VL8FmgTvfdm8igcaxpTe8yHAB+5/n1fU3JhnPjHAfJ7qgozo1LcZuQt8P6VlH/ xmVYiaE7dkd7MCu3oBRLEFIKmBWu93tuSFTfl+u7qvCVCvcPNwACSFsLlFTFJgo3vCcH BHN3eV2Y2d96iYig0VpdCjvDvxbunUqR81G2M= Original-Received: by 10.100.108.9 with SMTP id g9mr969636anc.137.1227412750755; Sat, 22 Nov 2008 19:59:10 -0800 (PST) Original-Received: by 10.100.13.13 with HTTP; Sat, 22 Nov 2008 19:59:10 -0800 (PST) In-Reply-To: Content-Disposition: inline X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) 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:105988 Archived-At: On Sun, Nov 23, 2008 at 04:56, dhruva wrote: > How about storing the machine IP address and the port in the file for > each successful emacs server instance. The file name itself can be > machine IP DOT port. This will handle the case of NFS mounted home > folders. I don't understand. What do you gain with this? How does emacsclient know with which instance must connect? > Another option, how about having a user defined fixed port for running > emacs server. This might lead to a DOS attack but the port is defined > by the user and hence not something that can be guessed easily. That was explicitly rejected while designing the TCP support for emacsclient/server. Juanma