Probably the "correct" way, if there is such a thing, to
handle this is to wrap the whole set of processes up into a job object and then
kill off the job object. You would have to really dig into it but that is one of
the big raves about using job objects, having like processes tied together so
you can smack them all in one fell swoop.
joe
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Baekelant, Erik
Sent: Wednesday, December 10, 2003 8:29 AM
To: '[EMAIL PROTECTED]'
Subject: [ActiveDir] OT: batch/command file and "child-processes" killing
Hello
First of all, apologies for going OT . . .
We are introducing our Scheduler software
(Client-side, CA Autosys) in the Windows environment.
Everything starts fine, except stopping/killing jobs.
Batch-file (a.cmd) calls another program (b.exe)....
a.cmd gets killed but b.exe keeps running.
It
is like (without using scheduler things) killing the batch and wanting the
"child-processes" to quit too.
Anyone any idea on how to execute b.exe from within a batch/command-file a.cmd ?
Much appreciated,
Erik
