Re: Caching Proxy for apt-get via http?
On Sun, May 06, 2001 at 03:05:12PM +0100, Andrew Suffield wrote: > On Sun, May 06, 2001 at 07:54:17AM +0200, Harald Dunkel wrote: > > Does anybody out there know what is the problem here? Maybe its > > the failure of Apache. What are your suggestions for running a > > cache for apt-get? > > Umm... how about "apt-proxy"? If you don't mind running (and debugging) experimental code.. Has a particularly hard time with round-robin mirrors not being in-sync, or (I think) occationally a mirror not supporting rsync access at all. Also has trouble with over-returning to the client. FE will return 5MB of a 200k deb.. And it requires rsync access to the repository. Despite all this, I did find it working a bit better on my dialup connection than squid was. Oh yeah, you'll want to give it a big cache, too. It doesn't seem to be able to clean its own cache properly. -- Ferret
Re: Caching Proxy for apt-get via http?
On Sun, May 06, 2001 at 07:54:17AM +0200, Harald Dunkel wrote: > Does anybody out there know what is the problem here? Maybe its > the failure of Apache. What are your suggestions for running a > cache for apt-get? Umm... how about "apt-proxy"? -- Andrew Suffield <[EMAIL PROTECTED]> pgp1umND2vBVo.pgp Description: PGP signature
Re: Caching Proxy for apt-get via http?
Harald Dunkel wrote: > > Brian May wrote: > > > > Have you told squid that it can use greater then 100MByte (the > > default)? > > > > I haven't tried Squid yet, cause Apache was already in place. > Of course I will try it. > I've got the same effect using Squid. When I tried to install Xpilot (just for testing of course :-), then some files (not all!) were not cached, as it seems. Of course I checked the cache size, the maximum file size, etc. ??? Regards Harri
Re: Caching Proxy for apt-get via http?
Brian May wrote: > > Have you told squid that it can use greater then 100MByte (the > default)? > I haven't tried Squid yet, cause Apache was already in place. Of course I will try it. Many thanx for your configuration hints. Regards Harri
Re: Caching Proxy for apt-get via http?
> "Harald" == Harald Dunkel <[EMAIL PROTECTED]> writes: Harald> Hi folks, To reduce network load and speed up upgrades I Harald> have installed a caching proxy on one of my machines Harald> (using Apache). But it doesn't work very well. Packages Harald> are downloaded from http.us.debian.org, even if they Harald> should have been taken from the cache due to an upgrade of Harald> another machine just a few minutes ago. Harald> The cache size is 300 MByte, so I doubt that this happens Harald> due to lack of space. And cheating Round Robin by using an Harald> IP address instead of 'http.us.debian.org' didn't help Harald> either. Have you told squid that it can use greater then 100MByte (the default)? (When I upgraded squid from unstable to stable, I told dpkg to install the new config file, with the low default limit. squid was automatically restarted, and it proceeded to remove files from my cache. Ooops. Something you have to watch out for) Harald> Does anybody out there know what is the problem here? Harald> Maybe its the failure of Apache. What are your suggestions Harald> for running a cache for apt-get? In my squid file, I put in refresh_pattern \.deb$ 43200 100%43200 refresh_pattern Release$720 100%720 refresh_pattern Packages.gz$720 100%720 refresh_pattern Sources.gz$ 720 100%720 to try and eliminate this problem. Seems to work fine. So far... -- Brian May <[EMAIL PROTECTED]>
Re: Caching Proxy for apt-get via http?
On Sun, May 06, 2001 at 07:54:17AM +0200, Harald Dunkel wrote: > Does anybody out there know what is the problem here? Maybe its > the failure of Apache. What are your suggestions for running a > cache for apt-get? As far as I am aware, Apache's caching functionality is rather primitive. Try Squid. -- - mdz
Caching Proxy for apt-get via http?
Hi folks, To reduce network load and speed up upgrades I have installed a caching proxy on one of my machines (using Apache). But it doesn't work very well. Packages are downloaded from http.us.debian.org, even if they should have been taken from the cache due to an upgrade of another machine just a few minutes ago. The cache size is 300 MByte, so I doubt that this happens due to lack of space. And cheating Round Robin by using an IP address instead of 'http.us.debian.org' didn't help either. Does anybody out there know what is the problem here? Maybe its the failure of Apache. What are your suggestions for running a cache for apt-get? Regards Harri