public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: victor romanchuk <rom@persimplex.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Hoping someone can help explain distcc to me
Date: Sun, 21 Aug 2011 05:34:37 +0400	[thread overview]
Message-ID: <4E5060AD.8030700@persimplex.net> (raw)
In-Reply-To: <CAEH5T2M4b0b4jmwebYkodpDA59c7K2PEw=-jNk2OAhHMiPu3Fw@mail.gmail.com>


> Both machines contain "distcc" in FEATURES. It's not using
> -march=native. I've tried various -jN values with no real difference
> in performance.

only client (your laptop) machine should be distcc featured. for server
(desktop) that feature is useless

> On the desktop, /etc/conf.d/distcc contains (among other things):
> DISTCCD_OPTS="${DISTCCD_OPTS} --allow 192.168.0.0/24"
> DISTCCD_OPTS="${DISTCCD_OPTS} --listen 192.168.0.100"

this is server distcc daemon configuration, one just instructs daemon on what
network interface to listen for incoming connections (interface with ip
192.168.0.100 in your case) and filter incoming distcc connections by source
address: allow only those coming from local network machines with ip addresses
192.168.0.1 to 192.168.0.254

then distccd have to be started: /etc/init.d/distccd start

> And /etc/distccd/hosts contains:
> 192.168.0.0/24

this file configures distcc client behavior (actually the configuration can be
complex, see distcc man page for details), but in trivial case (for home
computing) it might look like:

192.168.0.100/6 127.0.0.1/1

e.g the client is able to send up to 6 distcc jobs to 192.168.0.100 and limit to
one job at local machine. client's /etc/make.conf has to have distcc feature
enabled (FEATURES="distcc"). surely you can play with job distribution rules
around the network. `distcc --show-hosts` command displays what you configured.
the number of cuncurrently running jobs (-j flag) has to be not less than sum of
local and remote jobs

i had noticed that distcc is peevish about CFLAGS: these should be compatible on
both client and server. in my case i made these similar on both machines (laptop
is core2duo and desktop is core2quad; both are running  amd64 arch)

yet another way to install packages on weak notebook running it on the same arch
as desktop runs, - is to create binaries at powerful machine (while emerging or
with quickpkg utility) and share $PKGDIR with laptop

hth



  parent reply	other threads:[~2011-08-21  1:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-20 22:56 [gentoo-user] Hoping someone can help explain distcc to me Paul Hartman
2011-08-21  0:35 ` Peter Humphrey
2011-08-21  1:08   ` Paul Hartman
2011-08-21  1:58     ` Peter Humphrey
2011-08-21  2:46       ` Dale
2011-08-21  3:04         ` Matthew Finkel
2011-08-21  9:41           ` Peter Humphrey
2011-08-21 13:53             ` Joost Roeleveld
2011-08-21 16:27               ` Peter Humphrey
2011-08-21 17:42               ` Neil Bothwick
2011-08-24 11:04             ` Dale
2011-08-21  1:34 ` victor romanchuk [this message]
2011-08-21 10:38   ` Alex Schuster
2011-08-21 14:39     ` victor romanchuk
2011-08-22 20:41       ` Alex Schuster
2011-08-22 22:36         ` Bill Longman
2011-08-22 22:41         ` Bill Longman
2011-08-22 19:47 ` [gentoo-user] " Paul Hartman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E5060AD.8030700@persimplex.net \
    --to=rom@persimplex.net \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox