[distcc] why always compiling local if host not accessible ?

Martin Pool mbp at samba.org
Tue Jan 27 06:30:52 GMT 2004


On 27 Jan 2004, Heiko_Elger at arburg.com wrote:
> distcc: version 2.12
> OS: Windows XP Professional
> cygwin: latest version
> 
> Hello,
> 
> I'm sorry - I send this quistion again cause there was no response ...
> 
> Why is distcc always compiling locally if it cannot contact a distcc server?
> 
> IMHO it would be better if this job is requeued to the new host list, in which
> the not responding host is removed, instead of always be compiled on the
> localhost.

This is the designed behaviour.

It runs it locally mainly so that it does not waste a lot of time
trying other machines which might not be working.  It guarantees that
any single job will suffer at most one wasted connection attempt.

The jobs that have to be requeued locally should count against the
load of localhost, so even though the particular job will be local, it
creates a pressure for future jobs to be run elsewhere.

What kind of situation do you have that this is a big problem?
Normally there will be only one retry on each down machine every
minute, and running one extra job on localhost should not be a burden.

-- 
Martin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.samba.org/archive/distcc/attachments/20040127/9d2e88aa/attachment.bin


More information about the distcc mailing list