Thanks, I tried and it seems to be working, but now there is another side effect.
From time to time I get the following message:
distcc[18470] (dcc_select_for_read) ERROR: IO timeout
distcc[18470] (dcc_r_token_int) ERROR: read failed while waiting for token "DONE"
and the compilation frooze.
In the local machine I can see two process running:
18470 pts/0 S 0:00 distcc /usr/local/gcc-3.2.2/bin/g++ -pipe -Wall -Wove
18472 pts/0 S 0:00 /usr/bin/ssh remotemachine distccd --inetd
and in the remote machine, only the 'distccd' process is running.
Nothing else happens from there until I press Ctrl-C.
This is specially the case when I force several connection by using make -jN,
where N is twice or larger the number of real machines.
Marcelo
Martin Pool wrote:
On 6 Jul 2003, Marcelo Matus <[EMAIL PROTECTED]> wrote:
Hello:
First, let me say that I find distcc amazing, I am using it with three machines, including a laptop, a single CPU and and dual smp machine... it works great!
However, I have noticed that when I use the 'ssh' connection,
the 'master' machine shows several very busy 'distcc' processes
which seems to be waiting for the remote 'ssh' compilation process
to finish, ie, it seems 'distcc' is doing.
Thanks, this is a bug in 2.7.1 and fixed in 2.8cvs.
--
Martin
__ distcc mailing list http://distcc.samba.org/
To unsubscribe or change options: http://lists.samba.org/cgi-bin/mailman/listinfo/distcc
