Re: [gentoo-user] distcc not working
Try adding the port to
distcc-config --set-hosts 10.0.0.101:3632 10.0.0.103:3632
When i tried to use it without a port did not not work.
Catalin
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
--
gentoo-user@gentoo.org mailing list
Re: [gentoo-user] distcc not working
Joseph wrote:
On Sun, 2005-06-26 at 00:05 -0400, Boyd Stephen Smith Jr. wrote:
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.
It's very easy to not see DISTCC processes in distccmon-gnome when using
emerge, since it uses a private DISTCC_DIR.
I was monitoring any activity with distcc in top, gkrellm2 on eth0
Re: top
On the host or server? distcc takes very little time or memory on the
client side, so it might easily not show up on the client top display,
if compiling only occurs remotely.
That said, distccmon-gnome, should be run on the client, not the server.
Of course, gkrellm2 should probably works no matter what side you were on.
/etc/conf.d/distccd:
DISTCCD_OPTS=${DISTCCD_OPTS} --allow 10.0.0.103
This is on 10.0.0.101, right?
You also have 'DISTCCD_OPTS=${DISTCCD_OPTS} --allow 10.0.0.101 on
.103, right?
Yes, the 10.0.0.101 is the one on which compiling is started.
Well, distcc*d* is the daemon that answers requests. It has to be
properly configured (and started) on all the machines before distcc (the
client) works on any of them. [Okay, that's a simplification.]
Also, because distccd is incredibly insecure, you have to make sure and
specify all the clients you want the daemon to serve.
So, it your case, make sure .103 it set up to --allow .101 and vice-versa.
You have run /etc/init.d/distccd or rc-update add distccd default rc?
Does distcc work outside of emerge?
How do I check this one?
Run distcc from the command line. It should probably be in your path.
--
Boyd Stephen Smith Jr.
--
gentoo-user@gentoo.org mailing list
Re: [gentoo-user] distcc not working
On Sun, 2005-06-26 at 12:33 -0400, Boyd Stephen Smith Jr. wrote:
Joseph wrote:
On Sun, 2005-06-26 at 00:05 -0400, Boyd Stephen Smith Jr. wrote:
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.
It's very easy to not see DISTCC processes in distccmon-gnome when using
emerge, since it uses a private DISTCC_DIR.
I was monitoring any activity with distcc in top, gkrellm2 on eth0
Re: top
On the host or server? distcc takes very little time or memory on the
client side, so it might easily not show up on the client top display,
if compiling only occurs remotely.
That said, distccmon-gnome, should be run on the client, not the server.
Of course, gkrellm2 should probably works no matter what side you were on.
/etc/conf.d/distccd:
DISTCCD_OPTS=${DISTCCD_OPTS} --allow 10.0.0.103
This is on 10.0.0.101, right?
You also have 'DISTCCD_OPTS=${DISTCCD_OPTS} --allow 10.0.0.101 on
.103, right?
Yes, the 10.0.0.101 is the one on which compiling is started.
Well, distcc*d* is the daemon that answers requests. It has to be
properly configured (and started) on all the machines before distcc (the
client) works on any of them. [Okay, that's a simplification.]
Also, because distccd is incredibly insecure, you have to make sure and
specify all the clients you want the daemon to serve.
Yes, distcc is running an both machines.
So, it your case, make sure .103 it set up to --allow .101 and vice-versa.
Yes, on 10.0.0.101 in distccd configuration I have --allow 10.0.0.103
and other way around on .103 that is easy part.
You have run /etc/init.d/distccd or rc-update add distccd default rc?
distccd is in default so it runs at boot time.
Distcc was running fine before they forced --allow parameter in
configuration file as mandatory argument. So I modified
my /etc/conf.d/distccd with --allow parameter but it makes no
difference.
I've edit hosts as Catalin suggested but it makes no difference.
/etc/distcc/hosts:
10.0.0.103:3632 10.0.0.101:3632
Run distcc from the command line. It should probably be in your path.
Yes, it runs but in order to test it I need to compile something, the
argument is
distcc [COMPILER] [compile options] -o OBJECT -c SOURCE
So in my example if I want to test it on 10.0.0.101 machine I would
enter:
distcc 10.0.0.103:3632 -o ? -c ?
What do I put in place of OBJECT SOURCE?
--
#Joseph
--
gentoo-user@gentoo.org mailing list
Re: [gentoo-user] distcc not working
Need more info from clients and servers:
architectures of each machine
gcc versions
glibc versions
add
DISTCCD_OPTS=${DISTCCD_OPTS} --log-level info
to /etc/conf.d/distccd to each machine. Then check the client and
server syslogs whilst compiling.
If you have a firewall, is port 3632 allowed through?
BillK
On Sat, 2005-06-25 at 20:59 -0600, 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
--
#Joseph
--
--
William Kenworthy [EMAIL PROTECTED]
Home!
--
gentoo-user@gentoo.org mailing list
Re: [gentoo-user] distcc not working
On Sun, 2005-06-26 at 11:50 +0800, William Kenworthy wrote:
Need more info from clients and servers:
architectures of each machine
gcc versions
glibc versions
add
DISTCCD_OPTS=${DISTCCD_OPTS} --log-level info
to /etc/conf.d/distccd to each machine. Then check the client and
server syslogs whilst compiling.
If you have a firewall, is port 3632 allowed through?
BillK
I think is it is working now. I see some activity with gkrellm2 but
distccmon-text or distccmon-gnome not showing any job status on either
machine.
Yes, I've port 3632 open on both machines scan with nmap
gcc-3.3.5.20050130-r1
glibc-2.3.4.20041102-r1
--
#Joseph
--
gentoo-user@gentoo.org mailing list
Re: [gentoo-user] distcc not working
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=11189557171
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
Re: [gentoo-user] distcc not working
On Sat, 2005-06-25 at 20:16 -0700, Zac Medico wrote:
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=11189557171
Yes, I've seen all those post as well, top is not indicating any distcc
activity during compiling even though netstat -taupe is showing on
both machines:
tcp0 0 *:distcc*:* LISTEN distcc 2031788
19912/distccd
I know that distcc was working before ver. 2.18.3-r7
--
#Joseph
--
gentoo-user@gentoo.org mailing list
Re: [gentoo-user] distcc not working
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.
It's very easy to not see DISTCC processes in distccmon-gnome when using
emerge, since it uses a private DISTCC_DIR.
[Actually, this is the reason, I set up emerge with FEATURES-distcc
and export CCACHE_PREFIX=distcc instead.]
/etc/conf.d/distccd:
DISTCCD_OPTS=${DISTCCD_OPTS} --allow 10.0.0.103
This is on 10.0.0.101, right?
You also have 'DISTCCD_OPTS=${DISTCCD_OPTS} --allow 10.0.0.101 on
.103, right?
Does distcc work outside of emerge?
--
Boyd Stephen Smith Jr.
--
gentoo-user@gentoo.org mailing list
Re: [gentoo-user] distcc not working
On Sun, 2005-06-26 at 00:05 -0400, Boyd Stephen Smith Jr. wrote:
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.
It's very easy to not see DISTCC processes in distccmon-gnome when using
emerge, since it uses a private DISTCC_DIR.
[Actually, this is the reason, I set up emerge with FEATURES-distcc
and export CCACHE_PREFIX=distcc instead.]
I was monitoring any activity with distcc in top, gkrellm2 on eth0
/etc/conf.d/distccd:
DISTCCD_OPTS=${DISTCCD_OPTS} --allow 10.0.0.103
This is on 10.0.0.101, right?
You also have 'DISTCCD_OPTS=${DISTCCD_OPTS} --allow 10.0.0.101 on
.103, right?
Yes, the 10.0.0.101 is the one on which compiling is started.
Does distcc work outside of emerge?
How do I check this one?
When I setup a debug log via distccd this is what I got:
distccd[17477] (main) chdir to /tmp
distccd[17477] (dcc_setup_daemon_path) daemon's PATH is
/usr/i686-pc-linux-gnu/gcc-bin/3.3.5-20050130:/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin
distccd[17477] (dcc_should_be_inetd) stdin is a tty; assuming --daemon mode
distccd[17477] (dcc_listen_by_addr) listening on 0.0.0.0:3632
distccd[17477] (dcc_defer_accept) TCP_DEFER_ACCEPT turned on
distccd[17477] (dcc_standalone_server) 1 CPU online on this server
distccd[17477] (dcc_standalone_server) allowing up to 3 active jobs
distccd[17477] (dcc_ignore_sighup) ignoring SIGHUP
distccd[17481] (dcc_detach) setsid to session 17481
distccd[17481] (dcc_log_daemon_started) preforking daemon started (2.18.3
i686-pc-linux-gnu, built Jun 25 2005 20:40:58)
--
#Joseph
--
gentoo-user@gentoo.org mailing list
