From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Miles Lane <miles.lane@comcast.net>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: linux-2.4-benh -- rsync: failed to connect to rsync.penguinppc.org: Connection refused
Date: 10 Aug 2003 22:39:06 +0200 [thread overview]
Message-ID: <1060547946.595.36.camel@gaston> (raw)
In-Reply-To: <200308100818.53106.miles.lane@comcast.net>
On Sun, 2003-08-10 at 17:18, Miles Lane wrote:
> rsync -avz rsync.penguinppc.org::linux-2.4-benh .
> rsync: failed to connect to rsync.penguinppc.org: Connection refused
> rsync error: error in socket IO (code 10) at clientserver.c(83)
Some HW problems going on, fixed soon hopefully
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-08-10 20:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-10 15:18 linux-2.4-benh -- rsync: failed to connect to rsync.penguinppc.org: Connection refused Miles Lane
2003-08-10 20:39 ` Benjamin Herrenschmidt [this message]
2003-08-10 22:07 ` Ethan Benson
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=1060547946.595.36.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=miles.lane@comcast.net \
/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).