Re: getting distcc to compile without localhost

Ok, looks like this has been unnecessary.  The blank monitor output, 
(which started this whole adventure and all the second-guessing) appears 
to be a Gentoo problem, and a very old one at that:

http://bugs.gentoo.org/51616

As explained in that bug entry, by executing

DISTCC_DIR=/var/tmp/portage/.distcc distccmon-text 1

I get the correct output.  Sure enough, instead of fixing the problem, 
they put the step in their docs (which I had overlooked).


  --chris





Chris Robison wrote:
> Actually I think I may be misinterpreting the log output.
>
> I was noticing lots of lines like:
> distcc[19451] cpp libxslt.c on localhost completed ok
>
>
> ...which led me to believe that some work was being done on localhost. 
> But then just now I noticed it's also dumping lines like:
> distcc[19451] compile libxslt.c on 192.168.0.10/10 completed ok
>
> Different line, same filename. So, I don't think I'll continue this 
> thread until I'm certain of what I'm seeing.  To do that I think I 
> need to get the monitor running correctly, but I'll start another 
> thread for that.
>
> Thanks,
>
>  --chris
>
>
>
> Martin Pool wrote:
>> 2009/5/29 Chris Robison <[email protected]>:
>>  
>>> What is required to prevent distcc from using localhost?
>>>     
>>
>> Unless something is broken, with the setup you describe distcc will
>> only do compiles on the localhost when that's necessary - for example
>> for linking or writing profile data.  The log file will tell you why
>> it decided to run a job locally.
>>
>>
>>   
>
> __ distcc mailing list            http://distcc.samba.org/
> To unsubscribe or change options: 
> https://lists.samba.org/mailman/listinfo/distcc

__ 
distcc mailing list            http://distcc.samba.org/
To unsubscribe or change options: 
https://lists.samba.org/mailman/listinfo/distcc