[distcc] Compilation processes should die when interrupted.

[Martin Pool]

On 12 Sep 2002, Audun Ellertsen <audun at kscanners.no> wrote:

>    Remote compilation processes doesn't die when the local make is
>    interrupted, which is sometimes a problem when working with large
>    files.
> 
>    This is only a problem when I'm developing and have to make a
>    change to a file before the compilation is done. Then I have to
>    kill gcc on the other machines manually, or wait until they're
>    done, unless I can tolerate many gcc at once, which I can't with
>    the more memory expensive files.

Do they not die at all, or do they just run to completion and then go
away?

I have a plan to make compilers be killed off when the connection is
dropped.

-- 
Martin