[distcc] why always compiling local if host not acces sible ?

[Perochon Sebastien]

I don't know exactly your problem but here is a possible answer:

In my "host" file, I don't set "localhost" but use instead the name of my
computer in order to use it as remote like others computers.
The thing is doing that the compilation is done at "low" compared to
"normal" priority if set localhost.
So, CPU is using first to make the preprocess, ... of all the jobs and
compilation on localhost is done if some CPU is free.

Sébastien.

On 28 Jan 2004, Heiko_Elger at arburg.com wrote:

> >> And this is a problem because your local machine is very slow, or
> >> something like that?


> No my local machine is not slow (Intel Pentium 4 2.00GHz, 1 GB RAM),
> but if you start a make job and this make job takes a lot of time
> (1-2 hours) and you still want to work on this machine - every
> compile-job running make this machine slower. This is perhaps why
> it's a Windows XP with Cygwin running .... - it seems that
> preprocessing and compiling is hard job running on Cygwin ...

OK.  The slowdown is not really visible on Linux, at least for things
I build.  I guess Cygwin is not very efficient compared to either
system's native compiler.

I don't mind making it try another remote machine as the fallback.

-- 
Martin