Re: [MTT users] [MTT bugs] [MTT] #212: Generic networklockingserver *REVIEW NEEDED*

2010-03-05 Thread Ethan Mallove
On Fri, Feb/19/2010 12:00:55PM, Ethan Mallove wrote: > On Thu, Feb/18/2010 04:13:15PM, Jeff Squyres wrote: > > On Feb 18, 2010, at 10:48 AM, Ethan Mallove wrote: > > > > > To ensure there is never a collision between $a->{k} and $b->{k}, the > > > user can have two MTT clients share a $scratch, bu

Re: [MTT users] [MTT bugs] [MTT] #212: Generic networklockingserver *REVIEW NEEDED*

2010-02-19 Thread Ethan Mallove
On Thu, Feb/18/2010 04:13:15PM, Jeff Squyres wrote: > On Feb 18, 2010, at 10:48 AM, Ethan Mallove wrote: > > > To ensure there is never a collision between $a->{k} and $b->{k}, the > > user can have two MTT clients share a $scratch, but they cannot both > > run the same INI section simultaneously.

Re: [MTT users] [MTT bugs] [MTT] #212: Generic networklockingserver *REVIEW NEEDED*

2010-02-18 Thread Jeff Squyres
On Feb 18, 2010, at 10:48 AM, Ethan Mallove wrote: > To ensure there is never a collision between $a->{k} and $b->{k}, the > user can have two MTT clients share a $scratch, but they cannot both > run the same INI section simultaneously. I setup my scheduler to run > batches of MPI get, MPI instal