I've used distcc-2.9 before, but on my new machine I'm running 2.10-r3. My problem is that even though I can see that distcc is spreading jobs to several machines (and they get loaded and all) distccmon-text 5 does not output ANYTHING.. so the problem seems to be in distccmon-text (I have built it without gtk support). others have same problem - see URL. Reproducible: Always Steps to Reproduce: 1. 2. 3.
How are you starting distccmon-text?
In a command prompt as always, why? # distccmon-text 5 this just outputs what distcc jobs are running (or it should - it just displays no jobs(incl. a few blank lines) - try it with distcc-2.9 and you'll see how it works).
You have to define DISTCC_DIR. Read the distcc guide at http://www.gentoo.org/doc/en/distcc.xml#doc_chap6 code listing 6.1. So you could do: # DISTCC_DIR='`portageq envvar DISTCC_DIR`' distccmon-text 5 Providing you have read access to $DISTCC_DIR as the user you start distccmon with, you should have no problems.
Then howcome it just worked with distcc-2.9? stupid change? Anyways, the portageq envvar DISTCC_DIR returns blank - nothing. Where is this set - and why wasn't such a big change printed by the ebuild - as it is customary?
Found the DISTCC_DIR in /etc/conf.d/distccd - but first of all that directory wasn't even created (because the deamon hasn't been run before) - when I did and started the deamon - it still didn't work (the distccmon-text output) :( To serve distcc jobs to others, I don't need to run my own distccd now, do I? It all worked fine with 2.9. Anyways, thank you for your time and tips - once I find a solution, I'll post it in the thread I wrote about, so others can get their problem solved too.
Where have you defined DISTCC_DIR, if not in /etc/make.conf? The ebuild says there was a change, and what you had to do to get the thing to work. I was hoping that users would go to the website and look over the guide. It isn't feasable to write an essay in the ebuild to describe what precisely has changed.
/etc/conf.d/distccd is the configuration file for the Daemon, not the client (which makes the files the monitors can, monitor). You have to uncomment PORTAGE_TMPDIR in /etc/make.conf and add DISTCC_DIR=${PORTAGE_TMPDIR}/portage/.distcc to /etc/make.conf. You also have to mkdir that directory: /var/tmp/portage/.distcc chown portage:portage /var/tmp/portage/.distcc This is going to be fixed soon (see bug 29171) anyways.
Now exactly those few lines (not much is it?) is all that was needed to describe the changes from distcc-2.9 to distcc-2.10 - so distccmon-text would work for all of us ;) Btw. uncommented portage_tmpdir and added the distcc_dir var (in capital letters) - and created and chown'ed the dir - yet I still have no output in distccmon-text, although I can see it is talking to my distcc and distcc has spawned gcc processes on my other box.
It works now - I just didn't check that the DISTCC_DIR var actually got exported after entering it into /etc/env.d/02distcc and running env-update (sorry). after a little source /etc/profile it now works.
Hi Lisa, Please set this to resolved - I can't seem to do so :(
Don't get too reliant on DISTCC_DIR being in the env, as soon as bug 29171 and bug 29313 get committed it will be transparant to the user.
