X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 29 Feb 2012 10:27:43 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: 1.7.10/1.7.11: .Net programs started from a cygwin console may fail. Message-ID: <20120229092743.GQ23440@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4F4BA00E DOT 2020806 AT prover DOT com> <20120228125601 DOT GC23440 AT calimero DOT vinschen DOT de> <20120228141754 DOT GA6518 AT calimero DOT vinschen DOT de> <1113646302 DOT 20120229025114 AT mtu-net DOT ru> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1113646302.20120229025114@mtu-net.ru> User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Feb 29 02:51, Andrey Repin wrote: > Greetings, Corinna Vinschen! > > > Dead on, thanks! The definitions of tmp and temp in /etc/profile result > > in a double definition of the %TMP% and %TEMP% dos variables from the > > .Net applications POV and it's too dumb to handle that gracefully. > > > So the solution is, either we drop the tmp and temp definitions in > > /etc/profile, or old .net apps should be started only after calling > > `unset tmp temp' in bash. > > > Btw., tmp and temp are not preserved this way in tcsh's profile scripts. > > So I'm wondering why we do it in /etc/profile. Can somebody give me a > > management summary? > > I guess that was an attempt to fix something that isn't made things right, but > left there for years. > I would rather propose to solve it the other way around and use /etc/fstab > functionality to mount Cygwin's /tmp to current user's %TEMP% folder. > I don't know, how would that work in multi-user environment, though. POSIX tools usually expect that system paths are shared between processes. Consider client-server situations with shared files (sockets, fifos) in /tmp. So, no, this is not a generic solution for Cygwin tools. Any user or admin is free to do that locally, of course. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple