| Ian
Perfect! Using the scratch directory allowed me to have wine configs tied to the specific run so, as far as I can tell, no toes were stepped on while multiple runs were running on the same node.
Thanks Ian and Rich for the help on this - it's seriously opening up some doors for us!!!!!
Cheers, Mike On Mar 2, 2012, at 9:10 AM, Ian Chesal wrote:
Your best bet would be:
WINEPREFIX=$_CONDOR_SCRATCH_DIR
Then all your wine configs would be kept in the time dir Condor sets up on the machine at execution time. Unique to every job it running on the box.
Regards, - Ian
--- Ian Chesal
Cycle Computing, LLC Leader in Open Compute Solutions for Clouds, Servers, and Desktops Enterprise Condor Support and Management Tools
On Friday, 2 March, 2012 at 10:08 AM, Rich Pieri wrote:
Mike,
I'm not sure if WINE profiles are safe for concurrent instances. You may need to set different values for WINEPREFIX if you have concurrent instances on individual nodes.
-- MIT Laboratory for Nuclear Science
_______________________________________________ Condor-users mailing list subject: Unsubscribe You can also unsubscribe by visiting
The archives can be found at:
_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users
The archives can be found at:
https://lists.cs.wisc.edu/archive/condor-users/
|
![[Computer Systems Lab]](http://www.cs.wisc.edu/pics/csl_logo.gif){kind=logo}