This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: 1.7.10/1.7.11: .Net programs started from a cygwin console may fail.

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 ?

Andrey Repin ( 29.02.2012, <16:21>

Sorry for my terrible english...

Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]