|
List Info
Thread: LAM: lam Digest, Vol 693, Issue 1
|
|
| LAM: lam Digest, Vol 693, Issue 1 |
|
2006-05-18 09:50:31 |
|
Hi !
A little update to the latest message;
I removed the lam706 supplied with the RHEL4 installation and
downloaded+installed from RHN a 6.5.9 X86_64.
Magically, just by doing that, DYNA started working like a dream.
Now, the doubt is:
does a program built for using a version of lam (in this case 6.5.9)
work only with that particular version and NOT with higher versions ?
Or, are there some other problems not allowing the above ?
Puzzled.........
Cheers
Valter
lam-mpi.org"
type="cite">
On May 17, 2006, at 9:21 AM, Valter Dal Bo wrote:
I had a look at the /tmp/lam-debug-log.txt and I can see that the
process exits but without letting me know what is wrong with it
all............ :-( (The lam-debug-log.txt is inline at the bottom of
the msg....)
Does anybody have an idea on how to solve the problem ?
Any help will be greatly appreciated !
I'm not sure what you mean - the above information looks perfect.
Lamboot should exit when it's done, and it looks like it finished as
expected. It started a univers on the node "redhat2" with a "cpu
count" of 2. Once lamboot is finished, you can run lamnodes to see
what nodes are in the newly booted environment, mpirun to run
processes, and lamhalt to take down the environment. Are one of these
commands not working properly?
|
[1]
|
|
|
about | contact Other archives ( Real Estate discussion Medical topics )
|
lam-mpi.or