On 30 Aug 2006, Guy Isely <[EMAIL PROTECTED]> wrote: > Hi, > > I'm trying to use distcc to do distributed compilation across two machines > both > running Ubuntu. To set this up I did the following on both machines: > 1. Installed distcc from the repository > 2. Opened /etc/default/distcc, changed STARTDISTCC="false" to STARTDISTCC= > "true", and changed ALLOWEDNETS="127.0.0.1" to ALLOWEDNETS="127.0.0.1" " > 192.168.1.58" (or "192.168.1.57" on the other machine).
You need all values inside the one quoted string, e.g.: ALLOWEDNETS="127.0.0.1 192.168.1.58" also you must set LISTENER to the public interface of the machine, or unset it to listen on all addresses, e.g. LISTENER="" > 3. Opened /etc/environment and added a line that says: > DISTCC_HOSTS="localhost 192.168.1.58" (or "localhost 192.168.1.57" on the > 192.168.1.58 machine). > 4. Rebooted > > I checked on the 192.168.1.58 machine and found the distccd daemon is running > as follows: > /usr/bin/distccd --pid-file=/var/run/distccd.pid --log-file=/var/log/ > distccd.log --daemon --allow 127.0.0.1 --allow 192.168.1.57 --listen 127.0.0.1 > In fact, 4 copies of the same process are running simultaneously... I'm not > sure why. That's normal, it's just because that machine can run up to four jobs simultaneously. > distcc[5751] (dcc_writex) ERROR: failed to write: Connection refused This is the tip off: the connection is refused because the server is listening only for connections from localhost. I think this comes from Debian and it's reasonable there because they will prompt you for those values when the package is installed. Ubuntu doesn't do that and so it's a bit mysterious. Perhaps you could file a bug on launchpad.net explaining how you got into trouble. Thanks -- Martin __ distcc mailing list http://distcc.samba.org/ To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/distcc