[GE users] sgeexecd stop Doesn't Stop Jobs

Ron Chen ron_chen_123 at yahoo.com
Tue Oct 21 05:17:08 BST 2008


Even if the behaviour is intentional, I think it is not desired.

I think we should either let the shepherds running, or kill the job and shepherd.

Another *real important thing* is, when the execd restarts, does it reads back the jobs that are already running?

 -Ron


--- On Tue, 10/21/08, Daniel Templeton <Dan.Templeton at Sun.COM> wrote:
> I just noticed some behavior that doesn't seem right,
> and I wanted a 
> second opinion.  If I submit a job and then stop the
> execution daemon 
> where the job is running using "sgeexecd stop",
> the execution daemon and 
> the shepherd are killed, but the job itself keeps running. 
> If I ask 
> qacct what happened, it lists the job as having failed
> before writing 
> the exit status.  The behavior is the same for 6.0u10 and
> 6.2.
> 
> I seem to recall having had a conversation about this
> before, and I seem 
> to think that this behavior was intentional, so I'd
> like confirmation 
> one way or another before I file an issue.
> 
> Daniel
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> users-unsubscribe at gridengine.sunsource.net
> For additional commands, e-mail:
> users-help at gridengine.sunsource.net

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net




More information about the gridengine-users mailing list