[mvapich-discuss] Hard coded /tmp patch for shared memory files

[Lei Chai]

Hi John,

Thanks for reporting the problem and sending the patch to us. We have 
also realized the limitation, and have come up with a solution that does 
not require an actual file path for shared memory communication (by 
using shmget and shmat function calls, thanks to suggestions from TACC). 
The new solution will be available in the next mvapich2 release.

Thanks again,
Lei


John Partridge wrote:
> We recently had a customer issue with shared memory files being
> hard coded to /tmp. The circumstances were that the system was
> a diskless cluster with /tmp being an in memory files system.
>
> The /tmp file system was not large enough to support the shared
> memory files. So, the customer asked if we could make mvapich use
> an alternative path for the shared memory files.
>
> The version the customer is using is mvapich-0.9.9-1326 (from ofed-1.3)
> and  we produced a patch to get an alternative path via an environment
> variable. The patch is attached in case you might want to include it
> in a future release of mvapich/mvapich2
>
> Regards
> John
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> mvapich-discuss mailing list
> mvapich-discuss at cse.ohio-state.edu
> http://mail.cse.ohio-state.edu/mailman/listinfo/mvapich-discuss