Hello,
I've got a par-packed script on win32, and in task manager it looks like
this:
script.exe
\___par.exe
it script.exe seems to spawn par.exe process, which is the actual code.
This is all fine and dandy until you try running your script from win32
scheduler, because when you try to stop scheduler task, it kills
script.exe, but 'par.exe' is left there, running.
I'm looking for a way to avoid that, for example, to detect from 'par.exe'
that 'script.exe' has been killed... (or maybe script.exe would try to kill
all it's children when killed?)
--
Key fingerprint = 40D0 9FFB 9939 7320 8294 05E0 BCC7 02C4 75CC 50D9
The good Christian should beware of mathematicians,.... St Augustin
