On Nov 6, 2009, at 5:18 PM, Ethan Mallove wrote:
I'm running multiple MTT clients out of the same scratch directory
using SGE. I'm running into race conditions between the multiple
clients, where one client is overwriting another's data in the .dump
files - which is a Very Bad Thing(tm). I'm running the
client/mtt-lock-server, and I've added the corresponding [Lock]
section in my INI file. Will my MTT clients now not interfere with
each other's .dump files? I'm skeptical of this because I don't see,
e.g., Lock() calls in SaveRuns(). How do I make my .dump files safe?
Err... perhaps this part wasn't tested well...?
I'm afraid it's been forever since I've looked at this code and I'm
gearing up to leave for the Forum on Tuesday and then staying on for
SC09, so it's quite likely that you'll be able to look at this in more
detail before I will. Sorry to pass the buck; just trying to be
realistic... :-(
--
Jeff Squyres
jsquy...@cisco.com
