1 |
On Monday 29 January 2007 17:45, Daniel da Veiga wrote: |
2 |
> On 1/29/07, Alan McKinnon <alan@××××××××××××××××.za> wrote: |
3 |
> > On Monday 29 January 2007 11:15, Neil Bothwick wrote: |
4 |
> > > On Mon, 29 Jan 2007 00:47:47 -0800, kashani wrote: |
5 |
> > > > I wouldn't bother with a full mirror. Set a local rsync server that |
6 |
> > > > updates once a day and use http-replicator. That would be far less |
7 |
> > > > bandwidth than trying to keep a local dist server current. |
8 |
> > > |
9 |
> > > If daytime bandwidth is a particular issue, you can set up a cron |
10 |
> > > task on one of more machines (depending on the variety of packages in |
11 |
> > > use) to do |
12 |
> > > |
13 |
> > > emerge --sync && emerge -uDNf world |
14 |
> > > |
15 |
> > > to prime the cache during the night. That should reduce your daytime |
16 |
> > > downloads to almost zero. |
17 |
> > |
18 |
> > The daytime bandwidth is indeed the issue. This is South Africa, where |
19 |
> > technologically everything is top-notch first-world. Except for |
20 |
> > bandwidth. By local standards our pipe is quite big - a whopping 512k. |
21 |
> > Shared amongst two offices and 140 users. At least I get to do whatever |
22 |
> > I want with the bandwidth after hours - no real users to compete with, |
23 |
> > just their torrents :-) |
24 |
> > |
25 |
> > I already use a fairly complicate solution with emerge -pvf and wget in |
26 |
> > a cron on one of the fileservers, but it's getting cumbersome. And I'd |
27 |
> > rather not maintain an entire gentoo install on a server simply to act |
28 |
> > as a proxy. Would I be right in saying that I'd have to keep |
29 |
> > the "proxy" machine up to date to avoid the inevitable blockers that |
30 |
> > will happen in short order if I don't? |
31 |
> > |
32 |
> > I've been looking into kashani's suggestion of http-replicator, this |
33 |
> > might be a good interim solution till I can come up with something |
34 |
> > better suited to our needs. |
35 |
> |
36 |
> I'm using a different setup, of course its a small number of machines |
37 |
> (like 5 or 6), but it works great. I use NFS to mount |
38 |
> /usr/portage/distfiles on a server sharing this dir. Each time someone |
39 |
> request a file, it goes directly to the shared dir, being available |
40 |
> for all machines. This way, its only 1 request per new file, and only |
41 |
> files that are needed for update of the particular software most |
42 |
> machines have in common. |
43 |
|
44 |
I've set up rsyncd and Boa on the server machine (laptop) which has its |
45 |
portage and distfiles updated daily at the office. Then once a week or so I |
46 |
rsync the portage of the home machines with the laptop and they fetch any |
47 |
needed distfiles from the Boa server. For details regarding the set up of |
48 |
Boa there was a thread a year or so ago on this list. |
49 |
|
50 |
Of course there's the odd package that only exists on the LAN machines - they |
51 |
pull this off the Internet. They also insist downloading afresh certain |
52 |
binaries (e.g. Opera browser) and some CVS packages. I guess this is ebuild |
53 |
related, was thinking of looking into it with the thought of modifying it one |
54 |
day so that all available distfiles are pulled in from the Boa server. |
55 |
|
56 |
HTH. |
57 |
-- |
58 |
Regards, |
59 |
Mick |