=?GB2312?B?UmU6ILTwuLQ6ILTwuLQ6ILTwuLQ6IFtkaXN0Yw==?= =?GB2312?B?Y10gUHJvYmxlbSBhYm91dCBEaXN0Y2M=?= =?GB2312?B?IG9uIFdpbmRvd3Mgbm90IGN5Z3dpbiB0byBjb21waWxlIEFSTSBwcm9qZWN0?=

[Fergus Henderson]

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

>   That makes some sense, and this is no ADS installed on 192.168.0.232.
>
>
>
> But I still have a question about the
>
>
>
> > Distcc [5364] (dcc_check_backoff) still in backoff period for
> revo-lufei/4,lzo
>
>
>
> 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
fail,
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 --------------

3j?Zr???
???y??v?????