From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: dhruva Newsgroups: gmane.emacs.devel Subject: Re: error in server-running-p on M$ Date: Sun, 23 Nov 2008 09:26:09 +0530 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=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1227412590 11994 80.91.229.12 (23 Nov 2008 03:56:30 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 23 Nov 2008 03:56:30 +0000 (UTC) Cc: Eli Zaretskii , Ulrich Mueller , emacs-devel@gnu.org To: "Juanma Barranquero" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Nov 23 04:57: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 1L466F-0004yH-7S for ged-emacs-devel@m.gmane.org; Sun, 23 Nov 2008 04:57:31 +0100 Original-Received: from localhost ([127.0.0.1]:35839 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L4656-0007BM-8b for ged-emacs-devel@m.gmane.org; Sat, 22 Nov 2008 22:56:20 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1L464z-0007AR-La for emacs-devel@gnu.org; Sat, 22 Nov 2008 22:56:13 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1L464x-00079u-CM for emacs-devel@gnu.org; Sat, 22 Nov 2008 22:56:12 -0500 Original-Received: from [199.232.76.173] (port=50013 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L464x-00079r-5Y for emacs-devel@gnu.org; Sat, 22 Nov 2008 22:56:11 -0500 Original-Received: from rv-out-0708.google.com ([209.85.198.240]:52619) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1L464w-00024q-QN for emacs-devel@gnu.org; Sat, 22 Nov 2008 22:56:11 -0500 Original-Received: by rv-out-0708.google.com with SMTP id k29so1680994rvb.6 for ; Sat, 22 Nov 2008 19:56:09 -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=Um+YPuoZXH453YqssxOEjeO2Qij7ODwnbYiLSdYLWIo=; b=g/bDeGIPGITopjQQAWqeqexIsMBZohNIsLhTBVjFg6q0WKUtxiehHs/wzqS4cmRxQ4 GhQ5H7lWuFgrcC/LG+2VpJfQmWwFEmF7/1acHH7bTyolPrTCe1EqPSgx9ae/bgfs08qh D9d7tR0f7Mt9FP5tfWEZ2qtF1FPpbN0IwDfxM= 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=vbrwwOsvhUuTgCO2Fh0YYrJe/kxZurX2Yb8kkKpE91Mr66L8LZCNiI9j+f9JJ5BdaP Npn5RO783tNRX4r8dtHctvaA3+ExS4BOHPhzyRJ3a4Vtkztyx7VX+RTw9k90Ig3lBt96 rhVdxWe9K/URn35bkX3i69KyRBMr2tRAjMOjI= Original-Received: by 10.142.252.11 with SMTP id z11mr1021644wfh.166.1227412569630; Sat, 22 Nov 2008 19:56:09 -0800 (PST) Original-Received: by 10.142.110.21 with HTTP; Sat, 22 Nov 2008 19:56:09 -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:105987 Archived-At: Hi, On Sun, Nov 23, 2008 at 3:17 AM, Juanma Barranquero wrote: > On Sat, Nov 22, 2008 at 17:52, Ulrich Mueller wrote: > >> If you assume that the user's home directory is NFS mounted, then this >> is the normal case. > > It would be the normal case that the user, on the local machine, would > have the home directory in a NFS server, and at the same time, there > would be an Emacs on the NFS server using an authentication file on > the user's home directory? (That's the case you mentioned before, if I > understand it correctly.) If that really happens, that should be fixed > at another level... 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. 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. -dhruva -- Contents reflect my personal views only!