On Feb 19, 2005, at 4:09 AM, [EMAIL PROTECTED] wrote:
i re-install LAM from the source tarball (because i dont know how to[snipped]
rebulid LAM from LAM SRPMS), with step : (location at /usr/local/src/ not
3. re-install LAM from the source tarball (with the same step in computer
server).
That all looks good.
this is the file lamtest.err :
/var/spool/pbs/mom_priv/jobs/66.kimia-13.SC: line 19: lamboot: command not
found
/var/spool/pbs/mom_priv/jobs/66.kimia-13.SC: line 1: mpicc: command not found
/var/spool/pbs/mom_priv/jobs/66.kimia-13.SC: line 32: lamhalt: command not
found
This is the most telling. Your $PATH on the nodes does not include /usr/local/bin, so lamboot (and friends) are not being found. The LAM RPMs that come with OSCAR are set such that the use something called switcher and modules to set the path (and so on).
The easiest thing to do is to modify your $HOME/.basrhc (or whatever the shell startup file is for your shell) to include /usr/local/bin in your $PATH (and don't forget to set LD_LIBRARY_PATH for the intel fortran libraries!). However, this will only apply to just that one user.
If you want this to apply to all users, I'd recommend writing a simple modulefile that add on to the PATH and LD_LIBRARY_PATH. Search through the oscar-users and oscar-devel archives -- there have been several threads about this in the past.
--
{+} Jeff Squyres
{+} [EMAIL PROTECTED]
{+} http://www.lam-mpi.org/------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Oscar-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-users
