From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Is distfile partial mirror with failover possible?
Date: Mon, 4 Sep 2023 19:49:56 +0200 [thread overview]
Message-ID: <CAEdtorbpUw+NSaHeVM=FU2QKNP0if-cbwLxKXKVMTTbDjtHmow@mail.gmail.com> (raw)
In-Reply-To: <20230904182127.47147c1a@digimed.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1389 bytes --]
Quick n dirty solution:
put all distfiles on a central server
FS mount that remote dir to /var/cache/distfiles on all hosts
Alan
On Mon, Sep 4, 2023 at 7:21 PM Neil Bothwick <neil@digimed.co.uk> wrote:
> On Mon, 04 Sep 2023 14:04:53 +0100, Michael wrote:
>
> > On Monday, 4 September 2023 11:12:51 BST Walter Dnes wrote:
> > > I may be misunderstanding, but it seems to me that local mirrors are
> > > all-or-nothing. In the interests of saving bandwidth, I'd like to
> > > have a client first check the host's /var/cache/distfiles directory
> > > for a source tarball file. If not found, then fail over to another
> > > mirror as per GENTOO_MIRRORS in /etc/portage/make.conf. This would
> > > require emerge doing the lookup and potential failover for each file.
> > > Is this possible?
> >
> > Unless I misunderstand what you're asking, isn't this what takes place
> > anyway?
>
> The reference to a host makes me think Walter wants one machne to hold
> the distfiles for all on the network.
>
> > PS. Is http_replicator still available/maintained? I see the wiki
> > mentions apt-cacher-ng for local distfiles cache.
>
> I use apt-cacher-ng for this and it does what you are looking for.
>
>
> --
> Neil Bothwick
>
> The facts, although interesting, are usually irrelevant.
>
--
Alan McKinnon
alan dot mckinnon at gmail dot com
[-- Attachment #2: Type: text/html, Size: 1984 bytes --]
next prev parent reply other threads:[~2023-09-04 17:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 10:12 [gentoo-user] Is distfile partial mirror with failover possible? Walter Dnes
2023-09-04 13:04 ` Michael
2023-09-04 17:21 ` Neil Bothwick
2023-09-04 17:49 ` Alan McKinnon [this message]
2023-09-04 18:26 ` Neil Bothwick
2023-09-04 19:37 ` Alan McKinnon
2023-09-04 20:02 ` Mark Knecht
2023-09-04 21:20 ` Arve Barsnes
2023-09-05 16:34 ` Laurence Perkins
2023-09-05 2:54 ` Walter Dnes
2023-09-05 7:04 ` Neil Bothwick
2023-09-05 14:58 ` Walter Dnes
2023-09-05 15:07 ` Michael
2023-09-05 15:26 ` Neil Bothwick
2023-09-05 15:33 ` Walter Dnes
2023-09-05 18:28 ` Michael
2023-09-06 1:52 ` William Kenworthy
2023-09-05 9:06 ` hitachi303
2023-09-05 15:05 ` Michael
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='CAEdtorbpUw+NSaHeVM=FU2QKNP0if-cbwLxKXKVMTTbDjtHmow@mail.gmail.com' \
--to=alan.mckinnon@gmail.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