2009/8/26, Fulvio <[email protected]>: > Launching Rybka3 (mp.x64 with microwine) starts one process for each > core (4 in my case). > Then, when scid closes the engine, sends correctly a stop quit sequence, > but if rybka does not exit in time will send a kill command only to 1 > process. > So I remain 3 zombies running at 100%. > > The problem is in uci.tcl: > # last resort : try to kill the engine (TODO if Windows : no luck, > welcome zombies !) > if { ! $windowsOS } { catch { exec -- kill -s INT [ pid $pipe ] } } > > Commenting the line all works fine. > > Is it possible to have an option to disable the forced kill? (Maybe in > the engines configuration file)
I simply removed this line. I made some tests with all UCI engines I have and it has no drawback. Pascal ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Scid-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/scid-users
