From: "Frank Ch. Eigler" <fche@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: overseers@sourceware.org
Subject: Re: anonymous rsync
Date: Mon, 16 Feb 2015 16:01:00 -0000 [thread overview]
Message-ID: <20150216160101.GC21553@redhat.com> (raw)
In-Reply-To: <1424075773.23458.3.camel@bordewijk.wildebeest.org>
Hi -
> [...] I noticed the rsync connection gets reset more often the last
> couple of weeks. And in particular the last 12 hours all attempts
> got: rsync: read error: Connection reset by peer (104).
Like other resource-hungry anonymous resources, anon-rsync has
throttles such as connections-per-sourceip and connections-total.
These limits were bumped up for git:// recently and for rsync://
just now.
> Is there anything we can do to make this go smoother?
> Currently we are using the following crontab entry:
> 6 */2 * * * rsync -aHxhz --delete rsync://sourceware.org/mauve-cvs/ /mirror/cvsroot/mauve
You could use rsync-over-ssh with a (passphrase-less?) ssh-key
dedicated to "rsync --daemon" in your .ssh/authorized_keys.
- FChE
prev parent reply other threads:[~2015-02-16 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 8:36 Mark Wielaard
2015-02-16 16:01 ` Frank Ch. Eigler [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=20150216160101.GC21553@redhat.com \
--to=fche@redhat.com \
--cc=mark@klomp.org \
--cc=overseers@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).