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. %SystemRoot%/Temp then ? -- WBR, Andrey Repin (anrdae...@freemail.ru) 29.02.2012, <16:21> Sorry for my terrible english... -- 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
