On Apr 13, 2007, at 1:20 PM, Heroux, Michael A wrote:
> The only things I can say have changed are that I installed some
> new software yesterday, in particular Matlab.
>
> I am able to run my codes if I specify the RPI, e.g., "mpirun -ssi
> rpi crtcp ..." . It appears that modes crtcp, lamd and tcp work,
> but sysv and usysv do not.
>
> This is not a critical problem for me now, since I can run my
> programs, but I am puzzled about how the behavior changed.
That is odd. LAM/MPI uses very close to the maximum number of SysV
shared memory segments and semaphores allowed by default on OS X. If
other applications use some of these resources, LAM/MPI can end up
without enough to run. This is very common if a database server is
installed, but there could be other applications using them. You can
run the command "ipcs" to see what segments and semaphores are in use
(on some versions of 10.4, some people report you have to run as root
to see the full list). I would start there -- if there are a bunch
of resources already in use, boosting the defaults is probably your
best bet. Have a look at:
http://developer.postgresql.org/pgdocs/postgres/kernel-resources.html
for information on bumping the resources up.
Brian
--
Brian Barrett
LAM/MPI Developer
Make today a LAM/MPI day!
|
