Hello,
I recently sent a mail about a bug that annoys me, because I'm using lam
in a very particular way.
I deal with a lots of fast mpi jobs (sometimes just a few seconds) from
many differents users.
These jobs are can be very fast so that it is no-sense starting a new
lam session at each time (on my cluster a lamboot usually takes around 5
seconds).
Moreover I do not want to create as many accounts as I have different
users, so I only use one lam-session.
So if something goes wrong (crash, signal (CTRL+C)), it is difficult to
cleanup the session because other jobs could be running at the same time.
What could help me, is for example to be able to do a kind of lamclean,
but just for a given mpi job : for example
% lamclean lam_id
Maybe my approach is totally wrong.
What would you suggest me to handle this kind of situation ?
Thanks
Karl Forner
|
