From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Personal Gentoo mirror
Date: Thu, 6 Oct 2005 19:02:05 +0000 (UTC) [thread overview]
Message-ID: <loom.20051006T202539-885@post.gmane.org> (raw)
In-Reply-To: 1128590373.16504.63.camel@rattus
William Kenworthy <billk <at> iinet.net.au> writes:
> I'll also jump on board this - http-replicator works great. You build
> it from your existing distfile cache. You do not need the large mirror
> files as many, or rather most are unlikely ever to be accessed. Build
> it with what you already have, and just top it up as you go - if the
> file isnt already in your cache, its added when you download it.
> > http://gentoo-wiki.com/HOWTO_Download_Cache_for_LAN-Http-Replicator
What mechanisms can you employ to either limit the size of the stored files
or prune out the oldest files or the files that are completely obsolete
as new sources files exist in the distfile cache?
Is the distfile cache the same this as the CCACHE cache in the
make.conf file? If so then, CCACHE_SIZE="3G" could be used to
limit the cache size to 3 gigs, but, what mechanisms, short of
a script can be used to prune out old duplicate sources?
I guess the download cache is the complemetary companion to setting
up your own rsync mirror, as both allow for multiple systems to be
updated and synced off of an internal system and only one system
syncs or downloads new ebuilds/distfiles)?
I set this up both before, but I recall having to use aspects of
several documents. In the end, I abandoned syncing off of a single
system, as syncing update were sporadically successful, and the
scripts and cron entries were not amicable. I meant to get back to
this problem to sort it all out.
It'd be much simpler if a single document explained all the methods
and options and scripts, in a clear, consise manner to use a single
system for syncing,cache-ing, updateding, and pruning of disk space.
tmpwatch, distcleaner, distclean, yacleaner, repcacheman, dailysync.sh
just to mention a few script possibilities .
and the 4 basic URLs I looked at to try and sort things out:
http://www.gentoo.org/doc/en/rsync.xml?style=printable
http://gentoo-wiki.com/HOWTO_Local_Rsync_Mirror.
http://gentoo-wiki.com/Http_proxy
http://gentoo-wiki.com/HOWTO_Download_Cache_for_LAN-Http-Replicator
USE this URL to automate the updating of Gentoo workstations:
http://www.panhorst.com/glcu/
was yet another approach.
Any comments or suggestions as to the development of a single,
concise document, would be appreciated.
James
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2005-10-06 19:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-06 2:21 [gentoo-user] Personal Gentoo mirror Devraj Mukherjee
2005-10-06 2:28 ` John Jolet
2005-10-06 4:03 ` Rumen Yotov
2005-10-06 4:38 ` kashani
2005-10-06 5:06 ` Dave Nebinger
2005-10-06 3:09 ` Nick Rout
2005-10-06 9:19 ` William Kenworthy
2005-10-06 19:02 ` James [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=loom.20051006T202539-885@post.gmane.org \
--to=wireless@tampabay.rr.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