Dear LAM developers and users,
I noticed that in LAM 7.1.1 the -b option in lamboot seems to be ignored, and
the time required to lamboot is consequently comparable to that required by
lamboot without -b in LAM 7.0.2, this is a relevant excerpt from lamboot -d in
both cases:
LAM 7.1.1 with -b
n-1<644> ssi:boot:rsh: starting lamd on (nodo2)
n-1<644> ssi:boot:rsh: starting on n2 (nodo2): hboot -t -c lam-conf.lamd -d -s
-I "-H 172.20.21.1 -P 46432 -n 2 -o 0"
n-1<644> ssi:boot:rsh: launching remotely
n-1<644> ssi:boot:rsh: attempting to execute: rsh nodo2 -n 'echo $SHELL'
n-1<644> ssi:boot:rsh: remote shell /bin/bash
n-1<644> ssi:boot:rsh: attempting to execute: rsh nodo2 -n hboot -t -c
lam-conf.lamd -d -s -I '"-H 172.20.21.1 -P 46432 -n 2 -o 0"'
n-1<644> ssi:boot:rsh: successfully launched on n2 (nodo2)
LAM 7.1.1 without -b
n-1<570> ssi:boot:rsh: starting lamd on (nodo2)
n-1<570> ssi:boot:rsh: starting on n2 (nodo2): hboot -t -c lam-conf.lamd -d -s
-I "-H 172.20.21.1 -P 46407 -n 2 -o 0"
n-1<570> ssi:boot:rsh: launching remotely
n-1<570> ssi:boot:rsh: attempting to execute: rsh nodo2 -n 'echo $SHELL'
n-1<570> ssi:boot:rsh: remote shell /bin/bash
n-1<570> ssi:boot:rsh: attempting to execute: rsh nodo2 -n hboot -t -c
lam-conf.lamd -d -s -I '"-H 172.20.21.1 -P 46407 -n 2 -o 0"'
n-1<570> ssi:boot:rsh: successfully launched on n2 (nodo2)
while with lam 7.0.2 I had the following:
LAM 7.0.2 with -b
n0<32750> ssi:boot:rsh: starting lamd on (nodo2)
n0<32750> ssi:boot:rsh: starting on n2 (nodo2): hboot -t -c lam-conf.lamd -d -s
-I "-H 172.20.21.1 -P 46365 -n 2 -o 0"
n0<32750> ssi:boot:rsh: launching remotely
n0<32750> ssi:boot:rsh: -b used, assuming same shell on remote nodes
n0<32750> ssi:boot:rsh: got local shell /bin/bash
n0<32750> ssi:boot:rsh: attempting to execute "rsh nodo2 -n hboot -t -c
lam-conf.lamd -d -s -I "-H 172.20.21.1 -P 46365 -n 2 -o 0""
n0<32750> ssi:boot:rsh: successfully launched on n2 (nodo2)
LAM 7.0.2 without -b
n0<363> ssi:boot:rsh: starting lamd on (nodo2)
n0<363> ssi:boot:rsh: starting on n2 (nodo2): hboot -t -c lam-conf.lamd -d -s -I
"-H 172.20.21.1 -P 46385 -n 2 -o 0"
n0<363> ssi:boot:rsh: launching remotely
n0<363> ssi:boot:rsh: attempting to execute "rsh nodo2 -n echo $SHELL"
n0<363> ssi:boot:rsh: remote shell /bin/bash
n0<363> ssi:boot:rsh: attempting to execute "rsh nodo2 -n hboot -t -c
lam-conf.lamd -d -s -I "-H 172.20.21.1 -P 46385 -n 2 -o 0""
n0<363> ssi:boot:rsh: successfully launched on n2 (nodo2)
Is it a known issue? Sorry if the problem has already been solved or it depends
on my (wrong?) LAM configuration, I did not find anything related in the list
archives.
thank you for your help, Davide
FYI this is laminfo output, I can send more details if needed:
LAM/MPI: 7.1.1
Prefix: /usr/local/lam
Architecture: i686-pc-linux-gnu
Configured by: root
Configured on: Tue May 3 16:48:13 CEST 2005
Configure host: maialinux
Memory manager: ptmalloc2
C bindings: yes
C++ bindings: yes
Fortran bindings: yes
C compiler: gcc
C++ compiler: g++
Fortran compiler: pgf90
Fortran symbols: underscore
C profiling: yes
C++ profiling: yes
Fortran profiling: yes
C++ exceptions: no
Thread support: yes
ROMIO support: yes
IMPI support: no
Debug support: no
Purify clean: no
SSI boot: globus (API v1.1, Module v0.6)
SSI boot: rsh (API v1.1, Module v1.1)
SSI boot: slurm (API v1.1, Module v1.0)
SSI coll: lam_basic (API v1.1, Module v7.1)
SSI coll: shmem (API v1.1, Module v1.0)
SSI coll: smp (API v1.1, Module v1.2)
SSI rpi: crtcp (API v1.1, Module v1.1)
SSI rpi: lamd (API v1.0, Module v7.1)
SSI rpi: sysv (API v1.0, Module v7.1)
SSI rpi: tcp (API v1.0, Module v7.1)
SSI rpi: usysv (API v1.0, Module v7.1)
SSI cr: self (API v1.0, Module v1.0)
--
__________________________________________________________
Davide Cesari ARPA-Servizio Idro Meteorologico __
www http://www.arpa.emr.it/sim ---
Address: ARPA-SIM, Viale Silvani 6, 40122 Bologna, Italy
__________________________________________________________
|
