From: Andrew Morton <akpm@linux-foundation.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: [BUG?] sendfile / distcc
Date: Wed, 10 Sep 2008 23:44:29 -0700 [thread overview]
Message-ID: <20080910234429.1a8bfa1f.akpm@linux-foundation.org> (raw)
In-Reply-To: <1221038871.2442.86.camel@twins.programming.kicks-ass.net>
On Wed, 10 Sep 2008 11:27:51 +0200 Peter Zijlstra <peterz@infradead.org> wrote:
> Hi,
>
> I've been seeing this for a while now, but its still present with -rc5+
> kernels. Its always the local machine failing, never the remotes.
>
> [root@twins linux-2.6-rt]# nice ./k opteron build
> time distmake x86_64 O=opteron-build ARCH=x86_64
> testing twins: distccd running
> testing opteron: DOWN
> testing taijtu: distccd running
> testing dyad: distccd running
> testing lappy: host running
> testing ubuntu: host running
> DISTCC_HOSTS= twins/8 taijtu/32 dyad/32
> DISTCC_DIR=/dev/shm/distcc
> DISTCC_SLOTS=72
>
> ...
>
> distcc[9931] (dcc_writex) ERROR: failed to write: Connection reset by peer
> distcc[9931] Warning: failed to distribute /mnt/build/linux-2.6-rt/kernel/fork.c to twins/8, running locally instead
>
> ...
>
> distcc[12078] (dcc_pump_sendfile) ERROR: sendfile failed: Connection reset by peer
> distcc[12078] (dcc_readx) ERROR: unexpected eof on fd4
> distcc[12078] (dcc_r_token_int) ERROR: read failed while waiting for token "DONE"
> distcc[12078] Warning: failed to distribute /mnt/build/linux-2.6-rt/init/version.c to twins/8, running locally instead
>
distcc is very good at breaking networking. I assume 2.6.26 is OK?
next prev parent reply other threads:[~2008-09-11 6:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 9:27 [BUG?] sendfile / distcc Peter Zijlstra
2008-09-11 6:44 ` Andrew Morton [this message]
2008-09-11 8:26 ` Peter Zijlstra
2008-09-12 7:45 ` Peter Zijlstra
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=20080910234429.1a8bfa1f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).