tag 343922 + confirmed thanks Hi
On Sunday 18 Dec 2005 19:28, Andreas Krüger wrote: > With "df" and "du | sort -n", I quickly found out that > /var/cache/apt-proxy is much larger than I would like > it to be. > > A solution for bug #198859 would help... Yes, that bug is a very good idea, it's just not a high priority while there are bugs in the existing code. > As a workaround, I set, in /etc/apt/apt-proxy-v2.conf: > > cleanup_freq = 1d > max_age = 40d > > Both numbers had been considerably higher previously. > > I issued /etc/init.d/apt-proxy stop and > /etc/init.d/apt-proxy start, to make the two changes > valid immediately. > > I don't think I had a cache cleanup yesterday. Ouch. Thanks a lot for pointing this out. I have checked the code and you are right - the first cleanup cycle occurs at $cleanup_freq after apt-proxy is started. So in your case, you should work around the bug by setting cleanup_freq to less than the time you leave the machine powered on. Chris
