From: Ethan Benson <erbenson@alaska•net>
To: linuxppc-dev@lists•linuxppc.org
Subject: Re: linux-2.4-benh -- rsync: failed to connect to rsync.penguinppc.org: Connection refused
Date: Sun, 10 Aug 2003 14:07:21 -0800 [thread overview]
Message-ID: <20030810220721.GA19894@plato.local.lan> (raw)
In-Reply-To: <200308100818.53106.miles.lane@comcast.net>
On Sun, Aug 10, 2003 at 08:18:53AM -0700, 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)
its back up now.
I had to move everything over to a new disk, and didn't want anyone
pushing updates into thier rsync trees only to have the updates
mysteriously disappaer because they occured after that part of the
filesystem was dumped.
reason it took so long was /dev/hda was only getting about 97K per sec
transfer rates anymore.
everything is back up and much much faster.
--
Ethan Benson
http://www.alaska.net/~erbenson/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-08-10 22:07 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
2003-08-10 22:07 ` Ethan Benson [this message]
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=20030810220721.GA19894@plato.local.lan \
--to=erbenson@alaska$(echo .)net \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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