Date: Thu, 27 Jun 2002 23:42:10 +0200 From: David =?iso-8859-1?Q?Sieb=F6rger?= <drs@rucus.ru.ac.za> To: Philip Hallstrom <philip@adhesivemedia.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: FTP/HTTP caching proxy for use with fetch and ports? Message-ID: <20020627214210.GA79612@rucus.ru.ac.za> In-Reply-To: <20020627103338.C21360-100000@cypress.adhesivemedia.com> References: <20020627180641.S1497-100000@exile.ucc.ie> <20020627103338.C21360-100000@cypress.adhesivemedia.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu 2002-06-27 (10:37), Philip Hallstrom wrote: > I've got a small LAN (4 machines) and I tend to install a lot of > the same ports on all the machines (usually using portupgrade). What I've > been doing up till now is installing on one machine and then ftp'ing the > distfiles over to the other machines and installing on them. I know I > could build packages and do it that way, but for whatever reason I don't. > > I started looking into caching proxies that would help automate this > process somewhat, but I haven't had much luck. I tried jftpgw (FTP only) [snip] Here's an alternative idea. Use one machine to download distfiles and publish its /usr/ports/distfiles by either HTTP or FTP (say, http://master/distfiles/) then set: MASTER_SITE_OVERRIDE=http://master/distfiles/${DIST_SUBDIR} in /etc/make.conf on the others. They would try to fetch any distfiles they need from the local server before trying to download from the MASTER_SITES. The disadvantage is that distfiles downloaded by machines other than the master won't be shared automatically. Nor will files automatically expire, but /usr/ports/Tools/scripts/distclean.sh could be cron'ed to do that. On the plus side, it may be a little easier to set up. -- David Siebörger drs@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020627214210.GA79612>