Hi, there:
Below is the error occurred under cygwin on winxp fat32 platform.
It does not occur on winxp ntfs machines. So any idea to fix it?
IEL_at_xxxxx /usr/local/lam-7.0.6/bin
$ ./lamboot -v
LAM 7.0.6/MPI 2 C++ - Indiana University
n-1<3160> ssi:boot:base:linear: booting n0 (localhost)
n-1<3160> ssi:boot:base:linear: finished
IEL_at_xxxxx /usr/local/lam-7.0.6/bin
$ ./lamhalt
LAM 7.0.6/MPI 2 C++ - Indiana University
--------------------------------------------------------------------------
---
It seems that LAM was not able to remove a directory properly. This should
not happen, and will probably require manual intervention on your part.
tkill was trying to remove the following directory:
/tmp/lam-IEL_at_xxxxx
when some error occurred. Perhaps the following Unix error message will
help:
Unix errno: 90
Directory not empty
This directory contains some internal temporary LAM files, and is safe
to remove. Please go remove it manually.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
It seems that there is no lamd running on the host bird2.
This indicates that the LAM/MPI runtime environment is not operating.
The LAM/MPI runtime environment is necessary for the "lamhalt" command.
Please run the "lamboot" command the start the LAM/MPI runtime
environment. See the LAM/MPI documentation for how to invoke
"lamboot" across multiple machines.
-------------------------------------------------------------------
Above is the error message
After initiating lamhalt, the error occurs. The lamd process was not
shutdown and still has access to the /tmp/lam-IEL_at_xxx directory not
allowing users to remove the directory. The file lam-killfile was still
in the directory. Once the lamd process is killed manually from the Task
Manager, the lam-killfile is removed and the /tmp/lam-IEL_at_xxx directory
then becomes empty. Since the lamd process was shutdown, access to the
directory was returned to the system allowing users the ability to remove
the directory. The problem is consistent and repeats even if the session
directory is removed.
|
