[gentoo-user] Re: rsync internal mirror configuration

[James]

Dave Nebinger <dnebinger <at> joat.com> writes:


> This has some implications:

Ok, let's take it from the begining.

A. I followed step 4 in this document:

http://www.gentoo.org/doc/en/rsync.xml?style=printable

I was able to 'emerge sync' up a local client on the rsync server 
successfully,so that part is done. Here are my client entries in 
/etc/make.conf:

GENTOO_MIRRORS="192.168.2.9"
SYNC="rsync://192.168.2.9/gentoo-portage"

Test, per this document was successful, So now I can manually rsync
 up one system and then emerge sync all of the local gentoo 
clients manuallyor via cron (with crontab entries).

> 1. the /usr/portage directory is not updated by this process.
> You still need to emerge --sync the local system.  This is QED
> by a cron task.

OK on the local rsync server I added this to automate the daily 
task of rsync(ing)
# Rsync entries
#
30 1 * * * root emerge sync

Spartan but hopefully sufficent.

I have (3) other documents to follow (this should be one doc)
B) http://gentoo-wiki.com/HOWTO_Local_Rsync_Mirror.
C) http://gentoo-wiki.com/Http_proxy
D) 
http://gentoo-wiki.com/HOWTO_Download_Cache_for_LAN-Http-Replicator

(B) tells me how to edit the /etc/rsyncd.conf file and the
/etc/rsync/rsyncd.motd file. Also  I did these:
etc/init.d/rsyncd start
rc-update add rsyncd default

This mod was already made to each client's /etc/make.conf file:
SYNC="rsync://192.168.2.9/gentoo-portage

> 2. This only syncs up the /usr/portage tree but does not help reduce
> the number of distfiles downloads.
> Look at http://gentoo-wiki.com/Http_proxy

OK, now I use document (C) to create the proxy entry on each client:
Editing File: /etc/env.d/99local to look like this 
http_proxy="192.168.2.9:8080" 
instead of this  
http_proxy="proxy.server.com:8080"

I check it on the client by issuing "echo $http_proxy"
which give the correct results:
192.168.2.9:8080

So far so good???

> and http://gentoo-wiki.com/HOWTO_Download_Cache_for_
> LAN-Http-Replicator for
> instructions there.  By using the http-replicator you only will be
> downloading distfiles/patch files once.

OK here's where I use doc (D). http-replicator is masked so I 
# echo "net-proxy/http-replicator" >> /etc/portage/package.keywords
# emerge http-replicator
Which worked fine.

Then I added this line to the clients and the rsync(distfile) server:
http_proxy="http://192.168.2.9:8080"  per the doc (D).

On the server I ran:
'repcacheman --user portage --dir /var/cache/http-replicator' 
Then http-replicator start at boot:
rc-update add http-replicator default


and last run this daily on the server to keep it current?
emerge -uDva world && repcacheman

Anything I missed? The last part of doc (D) is a little fuzzy, 
especially the part about deleting duplicate and deleting the 
distfile directory.

???
Surely parts of all (4) documents belong in one master howto?


> 3. There is no additional disk space requirements for the rsync mirror;
> you're serving up your existing /usr/portage directory so it's not like you
> wouldn't have those files around anyway.
>

Yea, well I'll keep a close eye on this. I have the server set up, and one
client to update manually off of the server, It all goes well, I'll add more
systems, and automate via cron the system that stay up 24 hours a day.

Is there a script to update workstation systems, automatically,
 say 10 minutes after booting? How best to do this?

James


-- 
gentoo-user@g.o mailing list