Dale Emery wrote:
Hi!
> Is there a preference or option I can set, in either Scid or
> Rybka, to instruct Scid to kill ALL Rybka threads and not just
> the first one?
> I do not know such an option in Scid. However, I wonder if it's a
> bug in Rybka as Scid sends a proper quit signal to the engine once
> it is closed.
>
> I suppose that the culprit could also be microwine.
In case you could try to use the Wine delivered with your
Linux. I only have the free Rybka 2.2, but it runs fine in
wine delivered with Debian old stable (4.0 aka etch) as well
as the current stable (5.0 aka lenny). No difficult config
required.
> (I know I could set Rybka to use only 1 CPU, but I'd rather be
> able to run it at full capacity.)
> Does this really remove the zombi process you get once you close the
> analysis window?
>
> If I instruct Rybka to use only 1 CPU, it creates only 1 process, which
> Scid is able to shut down properly.
This is interesting nevertheless as, as I said I always get
a defunc zombie whatever engine I use, till the next engine
uses the same analysis slot and replaced the zombie process.
(It's not even limited to UCI but happens ot xboard engines
as well.) Probably Pascal has an idea what might be going on
here?
--
Kind regards, / War is Peace.
| Freedom is Slavery.
Alexander Wagner | Ignorance is Strength.
|
| Theory : G. Orwell, "1984"
/ In practice: USA, since 2001
------------------------------------------------------------------------------
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
Scid-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/scid-users
