Thanks, I'll try the version you recommend below!
Josh Hursey wrote:
Your previous email indicted that you were using r18241. I committed
in r18276 a patch that should fix this problem. Let me know if you
still see it after that update.
Cheers,
Josh
On Apr 29, 2008, at 3:18 PM, Sharon Brun
Your previous email indicted that you were using r18241. I committed
in r18276 a patch that should fix this problem. Let me know if you
still see it after that update.
Cheers,
Josh
On Apr 29, 2008, at 3:18 PM, Sharon Brunett wrote:
Josh,
I'm also having trouble using ompi-restart on a snap
Thank you for the advice, Jeff.
Best,
Linwei
On Apr 29, 2008, at 4:26 PM, Jeff Squyres wrote:
Alternatively, you can specify to install to a different location with
the --prefix option to configure (possibly somewhere you do have write
access).
On Apr 29, 2008, at 3:17 PM, Linwei Wang wrote:
Alternatively, you can specify to install to a different location with
the --prefix option to configure (possibly somewhere you do have write
access).
On Apr 29, 2008, at 3:17 PM, Linwei Wang wrote:
Yeah, it works.
Thank you all for the help.
Best,
Linwei
On Apr 29, 2008, at 4:00 PM, Al
Josh,
I'm also having trouble using ompi-restart on a snapspot made from a run
which was previously checkpointed. In other words, restarting a
previously restarted run!
(a) start the run
mpirun -np 16 -am ft-enable-cr ./a.out
<---do an ompi-checkpoint on the mpirun pid from (a) from another
Yeah, it works.
Thank you all for the help.
Best,
Linwei
On Apr 29, 2008, at 4:00 PM, Alberto Giannetti wrote:
Linwei, are you running the command as root?
Try using sudo:
# sudo make install
It will ask you for an administrator password.
On Apr 29, 2008, at 3:54 PM, Linwei Wang wrote:
Dea
Linwei,
I think you need to do
sudo make install
since you are trying to install into directories you don't have write
permission for.
Doug Reeder
On Apr 29, 2008, at 12:54 PM, Linwei Wang wrote:
Dear all,
I'm new to MPI... I'm trying to install open MPI on my mac (Leopard)..
But during
Hi,
> Making install in etc
> test -z "/usr/local/etc" || ../../config/install-sh -c -d "/usr/local/
> etc"
> /usr/bin/install -c -m 644 openmpi-mca-params.conf /usr/local/etc/
> openmpi-mca-params.conf
> install: /usr/local/etc/openmpi-mca-params.conf: Permission denied
> make[3]: *** [ins
Linwei, are you running the command as root?
Try using sudo:
# sudo make install
It will ask you for an administrator password.
On Apr 29, 2008, at 3:54 PM, Linwei Wang wrote:
Dear all,
I'm new to MPI... I'm trying to install open MPI on my mac (Leopard)..
But during the installation (with the
Dear all,
I'm new to MPI... I'm trying to install open MPI on my mac (Leopard)..
But during the installation (with the command "make install")
it keeps generating errors of "Permission denied" Anyone has an
idea of the reasons?
Part of the output is like:
"
Making install in etc
test -z "
Josh,
Thanks for the quick response. I'll test against some key applications
we would like to use blcr checkpointing/restarting against. Perhaps if
we're lucky and careful, we'll be able to get some near term use out of
what we have installed.
Sharon
Josh Hursey wrote:
Sharon,
This is, unfo
Sharon,
This is, unfortunately, to be expected at the moment for this type of
application. Extremely communication intensive applications will most
likely cause the implementation of the current coordination algorithm
to slow down significantly. This is because on a checkpoint Open MPI
do
Josh Hursey wrote:
On Apr 29, 2008, at 12:55 AM, Sharon Brunett wrote:
I'm finding that using ompi-checkpoint on an application which is
very cpu bound takes a very very long time. For example, trying to
checkpoint a 4 or 8 way Pallas MPI Benchmark application can take
more than an hour.
Josh,
Thanks for your inputs.
Yes, I'm able to restart properly outside the hostfile issues. The
problems were with the permissions on
/var/run/nscd/passwd
The hostfile issues have now also been resolved...the problem was
interactions with maui/torque's hostfile and getting a proper hostfile
The btl_tcp_sndbuf and btl_tcp_rcvbuf are limited by the kernel
(usually 128K), so there is no reason to set them to something huge,
if the kernel is unable to support these values. The eager didn't get
modified between 1.1 and 1.2, so it should work as expected.
george.
On Apr 28, 2008,
On Apr 29, 2008, at 12:55 AM, Sharon Brunett wrote:
I'm finding that using ompi-checkpoint on an application which is
very cpu bound takes a very very long time. For example, trying to
checkpoint a 4 or 8 way Pallas MPI Benchmark application can take
more than an hour. The problem is not w
Josh,
Yesterday at night I made some changes, checkout a new SVN version, and
revise completely the BLCR installation. It´s working fine. I suspect 2
different things:
1) cache or old files (configured with older BLCR version path) in
autom4te, configure or dependencies;
2) some miss config
SLIM H.A. wrote:
Is it possible to get information about the usage of hca ports similar
to the result of the mx_endpoint_info command for Myrinet boards?
The ibstat command gives information like this:
Port 1:
State: Active
Physical state: LinkUp
but does not say whether a job is actually usin
I'm finding that using ompi-checkpoint on an application which is very cpu bound takes a very very long time. For example, trying to checkpoint a 4 or 8 way Pallas MPI Benchmark application can take more than an hour. The problem is not where I'm dumping checkpoints (I've tried local and an nfs mou
19 matches
Mail list logo
