On 27 Jan 2004, [EMAIL PROTECTED] 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
signature.asc
Description: Digital signature
__ distcc mailing list http://distcc.samba.org/ To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/distcc
