From: "Walter Dnes" <waltdnes@waltdnes.org>
To: Gentoo Users List <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] An alternative to http-replicator
Date: Fri, 9 Jun 2006 23:31:54 -0400 [thread overview]
Message-ID: <20060610033154.GA22420@waltdnes.org> (raw)
We want to be "kinder and gentler" to the Gentoo mirrors. I have 2
machines; my main machine and a 1999 450 mhz PIII as "hot backup". I
try to keep the backup up to date with apps duplicating the main
machine, so that if the main machine dies, I can restore some data from
backups and be running in a couple of hours.
The procedure for "emerge --rsync" using the main machine as server is
simple. I'll now present my solution for /usr/portage/distfiles. This
obviously works best for machines with a similar set of apps. Run
emerge update on the server machine first. It'll get the tarballs it
needs, and they'll be sitting in /usr/portage/distfiles, waiting to be
served out to other machines in your LAN that need the same tarballs.
I use the "boa" webserver. It's lighweight, simple to configure, and
you can run multiple instances simultaneously. That is the best way to
separate privileges for different clients.
*IMPORTANT* Gentoo's emerge command always looks in the "distfiles"
folder below whatever URL it's given for a mirror. E.g. if I specify
"http://www.bad.example.com" as the mirror to use, emerge will look in
"http://www.bad.example.com/distfiles". The "Alias" declaration in
boa.conf handles this. The secondary machine's /etc/make.conf has the
line...
GENTOO_MIRRORS="http://192.168.123.252:1024 ftp://ftp.ndlug.nd.edu/pub/gentoo/ http://mirror.datapipe.net/gentoo"
so it'll try my main machine (192.168.123.252 on port 1024) first. I
invoke the portage server dedicated boa with the command...
boa -c /root/.boa/portage/
which implies that the config file to use is /root/.boa/portage/boa.conf
My /root/.boa/portage/boa.conf currently looks like so...
Port 1024
Listen 192.168.123.252
User nobody
Group nogroup
ErrorLog /var/log/boa/portage/error_log
AccessLog /var/log/boa/portage/access_log
DocumentRoot /usr/portage/distfiles/
UseLocaltime
DirectoryMaker /usr/lib/boa/boa_indexer
KeepAliveMax 1000
KeepAliveTimeout 10
MimeTypes /etc/boa/mime.types
DefaultType text/plain
Alias /distfiles /usr/portage/distfiles
Note that in addition to using a dedicated I/O port, the "portage
instance" of boa also has its own log files.
--
Walter Dnes <waltdnes@waltdnes.org> In linux /sbin/init is Job #1
My musings on technology and security at http://tech_sec.blog.ca
--
gentoo-user@gentoo.org mailing list
next reply other threads:[~2006-06-10 3:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-10 3:31 Walter Dnes [this message]
2006-06-10 4:43 ` [gentoo-user] An alternative to http-replicator Anielkis Herrera Gonzalez
2006-06-10 5:00 ` Michael Weyershäuser
2006-06-10 5:09 ` Teresa and Dale
2006-06-10 8:45 ` Neil Bothwick
2006-06-11 2:37 ` William Kenworthy
2006-06-12 23:17 ` Neil Bothwick
2006-06-10 6:09 ` Jeremy Olexa
2006-06-10 9:02 ` Michael Weyershäuser
2006-06-10 10:25 ` Mick
2006-06-11 1:41 ` Bob Sanders
2006-06-11 2:00 ` Teresa and Dale
2006-06-10 14:59 ` Jeremy Olexa
2006-06-10 17:19 ` Andrew Frink
2006-06-10 18:21 ` Uwe Thiem
2006-06-11 2:43 ` Walter Dnes
2006-06-11 3:06 ` Bob Sanders
2006-06-11 8:18 ` Mick
2006-06-12 2:24 ` Walter Dnes
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=20060610033154.GA22420@waltdnes.org \
--to=waltdnes@waltdnes.org \
--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