Signals would be a good way to approach this on a *nix OS, but Windows does not really do that. Can the target script listen on a socket or look for some pid.flag file(s) and then suspend/resume or exit itself? Can you give us some idea of what the target process is doing?
Cheers,
R.
In reply to Re: Stop,Suspend,Resume By Pid
by Random_Walk
in thread Stop,Suspend,Resume By Pid
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |