=?gb2312?B?tPC4tDogtPC4tDogtPC4tDogtPC4tDogW2Rpc3RjY10gUHJvYmxlbQ==?= =?gb2312?B?IGFib3V0IERpc3RjYyBvbiBXaW5kb3dzIG5vdCBjeWd3aW4gdG8gY29tcGk=?= =?gb2312?B?bGUgQVJNIHByb2plY3Q=?=

Feng Tan feng.tan at revoview.com
Wed Oct 8 04:34:47 GMT 2008

Thanks I¡¯ll do more testing this afternoon.

If any update I¡¯ll let u know.


Thanks again for your help.



·¢¼þÈË: Fergus Henderson [mailto:fergus at google.com] 
·¢ËÍʱ¼ä: 2008Äê10ÔÂ8ÈÕ 11:31
ÊÕ¼þÈË: Feng Tan
³­ËÍ: distcc at lists.samba.org
Ö÷Ìâ: Re: ´ð¸´: ´ð¸´: ´ð¸´: [distcc] Problem about Distcc on Windows not
cygwin to compile ARM project


2008/10/7 Feng Tan <feng.tan at revoview.com>

That makes some sense, and this is no ADS installed on


But I still have a question about the 


> Distcc [5364] (dcc_check_backoff) still in backoff period for


Why did this happen and how to avoid it?

This happens if distcc has previously, in the last minute or so, attempted
to send a compilation to that host and had the request fail.


You can temporarily avoid it by doing removing the contents of the "state"
and "lock" directories in your distcc directory (~/.distcc, or $DISTCC_DIR),

e.g. via "rm -rf ~/.distcc/state ~/.distcc/lock", before the start of your
build.  However, as soon as distcc next sends a request and has the request

it will then mark the host as "bad" for the backoff period (1 minute, IIRC),
and will avoid sending new requests to that host during the backoff period.


Fergus Henderson <fergus at google.com>

-------------- next part --------------
HTML attachment scrubbed and removed

More information about the distcc mailing list