Refrain from killing known protocol adapters
authorH.G.Muller <hgm@hgm-xboard.(none)>
Tue, 18 Jun 2019 09:05:10 +0000 (11:05 +0200)
committerH.G.Muller <hgm@hgm-xboard.(none)>
Tue, 18 Jun 2019 09:05:10 +0000 (11:05 +0200)
commit944b1c8d50a16f244ad043f67e15f4d5e3b7f3c4
treeca3f484d7153481c609bced0bc67ee2c51232f0c
parent36af1b5f5a0968f9a7b873fcca916c8f8f3ab587
Refrain from killing known protocol adapters

Killing 'engines' that run through an adapter and won't terminate fast
enough for XBoard's taste will always be very detrimental, as it will
kill the adapter, and leaves the actual engine (for which the adapter
was likely waiting) running, preventing the adapter would take action
against it. We will thus always refrain from killing engines when XBoard
knows they are running through an adapter, because it invoked the adapter
itself in response to the -f/sUCI option.
backend.c