From: Xi Shen <davidshen84@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] distcc does seem to work
Date: Wed, 30 Sep 2009 09:53:09 +0800 [thread overview]
Message-ID: <53e35fd50909291853p3d5fe998lf23e8362d67b085b@mail.gmail.com> (raw)
In-Reply-To: <20090929170758.AFD7BE078D@pigeon.gentoo.org>
thanks, i got it working now.
On Wed, Sep 30, 2009 at 1:08 AM, Al <al@ngale.adsl24.co.uk> wrote:
> Xi Shen wrote:
>
>> hi,
>>
>> this is the my 1st time working with distcc. after i have emerged and
>> configured the system (include the make.conf), i tried to emerge kde,
>> and use distmon-text to see what would happen. i lost the output of
>> the distmon-text, but the output looks something like this:
>>
>> somefile.name localhost[1]
>> somefile.name localhost[2]
>> somefile.name some.ip.i.configured[1]
>> somefile.name blocked
>>
> This looks normal I see the "blocked" when distcc is working but been too
> lazy to check it out.
>> is it the correct output? what does the '[1]' mean? what does 'blocked'
>> mean? and for most of the time, the 2nd field is 'localhost', does this
>> means most of the files are actually compiled on local? how to make it
>> distribute the work load to other host more than that of the local
>> one?
>>
>>
> Perhaps you could post your config- /etc/distcc/hosts, have you got the
> server running on the other box(s) what abut their configs
> -/etc/conf.d/distcc
>
> Al
>
>
--
Best Regards,
David Shen
http://twitter.com/davidshen84/
http://meme.yahoo.com/davidshen84/
next prev parent reply other threads:[~2009-09-30 2:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <dpmqY-25n-17@gated-at.bofh.it>
2009-09-29 17:08 ` [gentoo-user] distcc does seem to work Al
2009-09-30 1:53 ` Xi Shen [this message]
2009-09-28 11:11 Xi Shen
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=53e35fd50909291853p3d5fe998lf23e8362d67b085b@mail.gmail.com \
--to=davidshen84@googlemail.com \
--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