| 1 |
William Kenworthy <billk <at> iinet.net.au> writes: |
| 2 |
|
| 3 |
|
| 4 |
> I'll also jump on board this - http-replicator works great. You build |
| 5 |
> it from your existing distfile cache. You do not need the large mirror |
| 6 |
> files as many, or rather most are unlikely ever to be accessed. Build |
| 7 |
> it with what you already have, and just top it up as you go - if the |
| 8 |
> file isnt already in your cache, its added when you download it. |
| 9 |
|
| 10 |
> > http://gentoo-wiki.com/HOWTO_Download_Cache_for_LAN-Http-Replicator |
| 11 |
|
| 12 |
What mechanisms can you employ to either limit the size of the stored files |
| 13 |
or prune out the oldest files or the files that are completely obsolete |
| 14 |
as new sources files exist in the distfile cache? |
| 15 |
|
| 16 |
Is the distfile cache the same this as the CCACHE cache in the |
| 17 |
make.conf file? If so then, CCACHE_SIZE="3G" could be used to |
| 18 |
limit the cache size to 3 gigs, but, what mechanisms, short of |
| 19 |
a script can be used to prune out old duplicate sources? |
| 20 |
|
| 21 |
I guess the download cache is the complemetary companion to setting |
| 22 |
up your own rsync mirror, as both allow for multiple systems to be |
| 23 |
updated and synced off of an internal system and only one system |
| 24 |
syncs or downloads new ebuilds/distfiles)? |
| 25 |
|
| 26 |
I set this up both before, but I recall having to use aspects of |
| 27 |
several documents. In the end, I abandoned syncing off of a single |
| 28 |
system, as syncing update were sporadically successful, and the |
| 29 |
scripts and cron entries were not amicable. I meant to get back to |
| 30 |
this problem to sort it all out. |
| 31 |
|
| 32 |
It'd be much simpler if a single document explained all the methods |
| 33 |
and options and scripts, in a clear, consise manner to use a single |
| 34 |
system for syncing,cache-ing, updateding, and pruning of disk space. |
| 35 |
|
| 36 |
tmpwatch, distcleaner, distclean, yacleaner, repcacheman, dailysync.sh |
| 37 |
just to mention a few script possibilities . |
| 38 |
|
| 39 |
and the 4 basic URLs I looked at to try and sort things out: |
| 40 |
http://www.gentoo.org/doc/en/rsync.xml?style=printable |
| 41 |
http://gentoo-wiki.com/HOWTO_Local_Rsync_Mirror. |
| 42 |
http://gentoo-wiki.com/Http_proxy |
| 43 |
http://gentoo-wiki.com/HOWTO_Download_Cache_for_LAN-Http-Replicator |
| 44 |
|
| 45 |
USE this URL to automate the updating of Gentoo workstations: |
| 46 |
http://www.panhorst.com/glcu/ |
| 47 |
was yet another approach. |
| 48 |
|
| 49 |
|
| 50 |
Any comments or suggestions as to the development of a single, |
| 51 |
concise document, would be appreciated. |
| 52 |
|
| 53 |
James |
| 54 |
|
| 55 |
|
| 56 |
|
| 57 |
-- |
| 58 |
gentoo-user@g.o mailing list |
Archives