[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Condor-users] condor_rm and process killing on Windows
- Date: Mon, 20 Dec 2004 18:05:01 -0500
- From: "Ian Chesal" <ICHESAL@xxxxxxxxxx>
- Subject: RE: [Condor-users] condor_rm and process killing on Windows
> >When some.exe is running and he does condor_rm, condor is actually
> >killing the some.exe process -- the deepest process in the tree.
> >Leaving it's parent csh process thinking that some.exe finished and
> >that it should return a bunch of stuff to him over FTP.
> Nope, you're mixed up.
> When the execute machine is instructed to vacate (e.g. as a
> result of someone running condor_rm on a running job), condor
> sends WM_CLOSE messages to each process underneath the
> starter, regardless of their position in the "tree" (in fact,
> windows doesn't use process hierarchies at all).
> If you wanted to do something other than immediately exit
> when the WM_CLOSE message is posted to your process, you have
> to override the event handler (see
> ). I'm not aware of any way to do that using MKS csh or
> cmd.exe batch scripts, however.
Excellent. Then it must be the MSK csh shell's reponse to WM_CLOSE that
is giving us this very well-behaved shut down, waiting for spawned
children to close properly.