On Mon, Jun 11, 2007 at 07:36:24AM -0400, Theo Van Dinter wrote: > So I'm thinking we should get some more mirrors for the channel setup to > distribute the load. Coral sucked, so let's not use them. I also don't want > to add in the zones machine since we already use a large amount of resources > there anyway. Apache dist isn't viable since it keeps the old versions > around.
Hey folks,
So there were some mails from people volunteering. I think this is great,
thanks! We don't have any real documentation for this yet, but here's the
basics:
- Setup rsync to pull the updates and store them wherever you want. The
cronjob/etc that runs rsync should run it semi-frequently, I recommend every
15 minutes or so -- pick a random starting minute:
2,17,32,47 * * * * rsync -rq --delete rsync.spamassassin.org::updates
/path/to/updates
- Have a webserver that serves up "/path/to/updates". You may want to not
allow directory listings. It's not necessary for sa-update, and keeps
crawlers and such at bay. Using Apache httpd, you could do something like:
<location /updates>
Options none
</location>
- Let [EMAIL PROTECTED] know that there's a new mirror and what
the URL is. If you'd prefer it to have a different priority
(higher/lower) than other mirrors, let us know that too.
- We add the URL to the MIRRORED.BY file, which makes the mirror live.
One person asked what the expected load is for running a mirror. It's pretty
light. A month's worth of requests (~535k) right now is ~15G, which breaks
down to ~18000 requests/day and ~6KB/sec.
--
Randomly Selected Tagline:
"Do not marry a person that you know that you can live with; only marry
someone that you cannot live without." - Unknown
pgpgHqnKBMi38.pgp
Description: PGP signature
