2008/2/11 John Vogel <[EMAIL PROTECTED]>:
> The only issue now is that terminateProcess doesn't always terminate
> netstat.exe in the cmd.exe so I don't get an exit condition.
A simple way is to use runInteractiveProcess instead of
runInteractiveCommand. The former doesn't start a new cmd.exe but
John Vogel wrote:
Thankyou both Don Stewart and Simon Marlow for your responses.
By adding yield and threadDelay in certain spots I have at least prevented
some of the threads from being starved of CPU time.
The only issue now is that terminateProcess doesn't always terminate
netstat.exe
>
> Thankyou both Don Stewart and Simon Marlow for your responses.
By adding yield and threadDelay in certain spots I have at least prevented
some of the threads from being starved of CPU time.
The only issue now is that terminateProcess doesn't always terminate
netstat.exe in the cmd.exe so I
John Vogel wrote:
I am running my program in WinXP with ghc 2.6.8
If you install netstat and change the parameters it should still work in
linux.
Why does thread # 3 dominate over the over threads int the output?
Why does thread # 4 never seem to run?
I can't use the sleep function in Syste
jpvogel1:
>I am running my program in WinXP with ghc 2.6.8
>
>If you install netstat and change the parameters it should still work in
>linux.
>
>Why does thread # 3 dominate over the over threads int the output?
>Why does thread # 4 never seem to run?
>
>I can't use the
I am running my program in WinXP with ghc 2.6.8
If you install netstat and change the parameters it should still work in
linux.
Why does thread # 3 dominate over the over threads int the output?
Why does thread # 4 never seem to run?
I can't use the sleep function in System.Process.Win32 since
