From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: emacs client/server mode hardcodes /tmp path Date: Tue, 28 Oct 2008 10:29:39 -0400 Message-ID: References: <18695.5574.107271.711561@a1i15.kph.uni-mainz.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1225204205 16070 80.91.229.12 (28 Oct 2008 14:30:05 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 28 Oct 2008 14:30:05 +0000 (UTC) Cc: emacs@gentoo.org, Diego Petteno , emacs-devel@gnu.org To: Ulrich Mueller Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 28 15:31:06 2008 connect(): Connection refused 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 1Kupax-0007Hu-VN for ged-emacs-devel@m.gmane.org; Tue, 28 Oct 2008 15:30:56 +0100 Original-Received: from localhost ([127.0.0.1]:50074 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KupZs-0007KJ-43 for ged-emacs-devel@m.gmane.org; Tue, 28 Oct 2008 10:29:48 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KupZn-0007JC-0g for emacs-devel@gnu.org; Tue, 28 Oct 2008 10:29:43 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KupZl-0007HA-Hq for emacs-devel@gnu.org; Tue, 28 Oct 2008 10:29:42 -0400 Original-Received: from [199.232.76.173] (port=57763 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KupZl-0007H0-BM for emacs-devel@gnu.org; Tue, 28 Oct 2008 10:29:41 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:62424) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KupZk-0007Ps-QB for emacs-devel@gnu.org; Tue, 28 Oct 2008 10:29:41 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhAFABO+BklMCqyo/2dsb2JhbACBdr11AYorglUBeYEN X-IronPort-AV: E=Sophos;i="4.33,499,1220241600"; d="scan'208";a="28958282" Original-Received: from 76-10-172-168.dsl.teksavvy.com (HELO pastel.home) ([76.10.172.168]) by ironport2-out.teksavvy.com with ESMTP; 28 Oct 2008 10:29:39 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 4403E8E6F; Tue, 28 Oct 2008 10:29:39 -0400 (EDT) In-Reply-To: <18695.5574.107271.711561@a1i15.kph.uni-mainz.de> (Ulrich Mueller's message of "Tue, 28 Oct 2008 14:38:14 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. 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:105074 Archived-At: >>> I'm working to make use of pam_mktemp in my systems by default, >>> pam_mktemp is a PAM module that creates a private temporary >>> directory per-user inside /tmp and sets TMP and TMPDIR accondingly. >> Indeed. I'm not sure what should be done here. The reason for the >> hard-coded /tmp is that the emacsclient process and the emacs server >> process may be executed from different contexts (different login >> sessions for example), so it's not clear that they would use the >> same $TMPDIR setting. >> What do others think? Should we take the risk and obey $TMPDIR? Yes, I think we should obey TMPDIR (of course consistently between emacsclient.c and server.el). Stefan