Joseph wrote: > I'm reading all the posts regarding distcc and it seems to me everything > is simple but for some reason or another I don't see any activity with > distccmon-gnome across my network. > > make.conf: > MAKEOPTS="-j3" > FEATURES="distcc" > > /etc/conf.d/distccd: > DISTCCD_OPTS="${DISTCCD_OPTS} --allow 10.0.0.103" > > /etc/distcc/hosts > 10.0.0.103 10.0.0.101 > > 10.0.0.101 - is localhost > 10.0.0.103 - is remote computer (faster) > > Both machines are AMD
If you run "top" on a distcc node, can you see the compiler processes? You might find something useful in this recent thread: http://marc.theaimsgroup.com/?t=111895571700001
michael higgins wrote: > On Thu, 16 Jun 2005 14:08:46 -0700 > Zac Medico <[EMAIL PROTECTED]> wrote: > > > > michael higgins wrote: > > > > > I have a couple of questions about using distcc. I have two machines. One > > > is \ > > > significantly faster than the other, both x86 (pentium 2 and amd > > > athlon-xp). > > > First, a big thanks to all who replied. > > > > > I've followed the http://www.gentoo.org/doc/en/distcc.xml instructions > > > for \ > > > configuring portage to use distcc. Should I need to continue with the \ > > > instructions for "working with automake"? > > > > Portage does this automatically as long as you have the corresponding > > FEATURES \ > > enabled. > > > This is what I was hoping to hear. > > > > > Also, how do I tell the faster machine to just use it's own power and not > > > \ > > > attempt to use the slower one? > > > > When you run distcc-config --set-hosts on the faster machine you want to > > exclude \ > > the slower machine. > > > > > I tried so far, getting distccd running on both machines, each > > > distcc-config \ > > > --set-hosts has one IP entry, that of the other machine. Is this right? > > > > You may want to include localhost. > > > Interesting... I wonder why? > Well, sometimes you may not want to include localhost. Maybe it has enough load \ already. > > > > I ran distcc-gnome and saw no activity reported on the faster machine > > > when \ > > > emerging something on the slower one. So, it would seem it's not working. > > > > > > Can anyone give me some hints? The manpage for distcc doesn't seem (to > > > me) to \ > > > be much related to the gentoo how-to... '-) > > > TIA, > > > > > > > #!/bin/bash > > source /etc/make.globals > > source /etc/make.conf > > export DISTCC_DIR="${PORTAGE_TMPDIR}/portage/.distcc" > > exec /usr/bin/distccmon-gnome > > > > > So, I just installed a package on the faster machine. It did try to use > another, \ > but found none and compiled locally, but spit out an error. Maybe adding > localhost \ > will fix this? If the faster machine isn't going to use any distcc nodes (other than localhost) then \ you should remove distcc from FEATURES. > I tried emerging the same package on the slower machine and running this > script \ > above. Nothing came up in it. However, I noticed that each time the compiler > went \ > to run something, there was network activity. 'top' on the faster machine > showed \ > distccd working and launching the compiler, afaict. You can enable logging in /etc/conf.d/distccd. > So, I have to wonder if/why the monitors don't work for me... > export DISTCC_DIR="${PORTAGE_TMPDIR}/portage/.distcc" works for me. Maybe it will \ help if you use "lsof" to find out what files distcc has open. > Next time I'll just set the debug level and log location to see what actually > \ > happened. > Thanks again, foax. > > -- gentoo-user@gentoo.org mailing list