Oops! The times that were sent were wrong. Here's the correct times:
- 3:00am-09:00am Pacific US time
- 4:00am-10:00am Mountain US time
- 5:00am-11:00am Central US time
- 6:00am-12:00am Eastern US time
- 11:00am-05:00pm GMT
On Dec 21, 2012, at 12:44 PM, Jeff Squyres wrote:
> Our Indiana U. ho
Our Indiana U. hosting providers will be doing some maintenance over the
holiday break.
All Open MPI services -- web, trac, SVN, ...etc. -- will be down on Wednesday,
December 26th, 2012 during the following time period:
- 5:00am-11:00am Pacific US time
- 6:00am-12:00pm Mountain US time
- 7:00a
Thanks for help. All work as you said.
On Fri, Dec 21, 2012 at 7:11 PM, Ralph Castain wrote:
> Don't know how many times I can repeat it, but I'll try again: you are not
> allowed to reuse a collective id. If it happens to work, it's by accident.
>
> If you want to implement multiple modex/barri
Hi,
additional to the patches used for building on cygwin
openmpi-1.7rc5, a new one is needed for openmpi-1.9a1r27710 build.
See attached for statfs usage.
As config parameters, I added "if-windows,shmem-windows"
to
--enable-mca-no-build=paffinity,installdirs-windows,timer-windows,shmem-sysv,if-
Don't know how many times I can repeat it, but I'll try again: you are not
allowed to reuse a collective id. If it happens to work, it's by accident.
If you want to implement multiple modex/barrier operations, they each need to
have their own unique collective id.
On Dec 20, 2012, at 9:28 PM,
Actually, if I reuse id's in equivalent calls like this:
...
'modex' block;
'modex' block;
'modex' block;
...
or
...
'barrier' block;
'barrier' block;
'barrier' block;
...
there is no hanging. The hang only occurs if this "reusing" follows after
using of another collective id, In the way I wrot
