On 4 Jan 2004 at 11:34, Autrijus Tang wrote:?? Ignored, as in PAR_CLEARTEMP=0 ?Also implemented is that PAR_CLEARTEMP is ignored when PAR_TEMP is explicitly set by user, to avoid race conditions.
Yes.
How does using a different temp base location create a race condition that doesn't exist with the default?
Because, $PAR_TEMP is not the "temp base location" for working directories (that's $TEMP)... It _is_ the working directory.
So if $PAR_TEMP is set to "C:\internal", that is where the files will go, instead of "$TEMP\par-$USER\temp-$MTIME". Thus, if two or more instances are launched simultaneously, they will all use "C:\internal" as their final storage place.
As file names are chosen based on crc32, collision is usually not a problem. However, that directory cannot be cleaned or removed, since other instances may will be running. So PAR_CLEARTEMP has to be disabled in that case.
If you'd like to modify the temp base location, set $TEMP will probably be a better choice...
Thanks, /Autrijus/
