My apologies, should have been a bit more clear. So the users home directories reside on the lustre filesystem. They login and start some computational job in the foreground. When their session times out or they get disconnected their jobs are still running and need to be killed by sending the kill signal. The job should also die with the session if it is running in the foreground.
-J On Fri, Jun 18, 2010 at 10:55 AM, Jagga Soorma <jagg...@gmail.com> wrote: > Hey Guys, > > Some of my users are reporting that sessions that they start on the lustre > cluster seem to live on if their session times out, or if they otherwise get > disconnected. This even happens when the session was in the foreground. > Could the shared lustre fs be causing this? Any ideas? > > Thanks, > -J >
_______________________________________________ Lustre-discuss mailing list Lustre-discuss@lists.lustre.org http://lists.lustre.org/mailman/listinfo/lustre-discuss