| 1 |
On Monday 29 January 2007 11:15, Neil Bothwick wrote: |
| 2 |
> On Mon, 29 Jan 2007 00:47:47 -0800, kashani wrote: |
| 3 |
> > I wouldn't bother with a full mirror. Set a local rsync server that |
| 4 |
> > updates once a day and use http-replicator. That would be far less |
| 5 |
> > bandwidth than trying to keep a local dist server current. |
| 6 |
> |
| 7 |
> If daytime bandwidth is a particular issue, you can set up a cron |
| 8 |
> task on one of more machines (depending on the variety of packages in |
| 9 |
> use) to do |
| 10 |
> |
| 11 |
> emerge --sync && emerge -uDNf world |
| 12 |
> |
| 13 |
> to prime the cache during the night. That should reduce your daytime |
| 14 |
> downloads to almost zero. |
| 15 |
|
| 16 |
The daytime bandwidth is indeed the issue. This is South Africa, where |
| 17 |
technologically everything is top-notch first-world. Except for |
| 18 |
bandwidth. By local standards our pipe is quite big - a whopping 512k. |
| 19 |
Shared amongst two offices and 140 users. At least I get to do whatever |
| 20 |
I want with the bandwidth after hours - no real users to compete with, |
| 21 |
just their torrents :-) |
| 22 |
|
| 23 |
I already use a fairly complicate solution with emerge -pvf and wget in |
| 24 |
a cron on one of the fileservers, but it's getting cumbersome. And I'd |
| 25 |
rather not maintain an entire gentoo install on a server simply to act |
| 26 |
as a proxy. Would I be right in saying that I'd have to keep |
| 27 |
the "proxy" machine up to date to avoid the inevitable blockers that |
| 28 |
will happen in short order if I don't? |
| 29 |
|
| 30 |
I've been looking into kashani's suggestion of http-replicator, this |
| 31 |
might be a good interim solution till I can come up with something |
| 32 |
better suited to our needs. |
| 33 |
|
| 34 |
Thanks |
| 35 |
|
| 36 |
alan |
| 37 |
|
| 38 |
-- |
| 39 |
gentoo-user@g.o mailing list |
Archives