Bug#172777: apt: increasing APT::Cache-Limit fixes it
Followup-For: Bug #172777
Jochen followed up with the obvious pulling a source out of sources.list,
but says it would show up a couple of days later. I figure this is because
number of packages in the remaining lists still increased.
One desktop, the one with the most sources in sources.list, ran into
this. Plenty of memory and swap still available. Another system hasn't
yet developed this problem. The one with the problem was getting a
Speicherzugriffsfehler ( segfault? ).
I increased the Cache-Limit, 'APT::Cache-Limit=104857600;', as suggested
in bug #172726, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=172726
and that fixed the problem.
After it worked once, I was able to leave the Cache-Limit increase off the
command line and not get the problem.
Um, we've got a lot of packages out there. It seems we need to thank the
debian developers for packaging so many programs that we run into this
Can we move to a larger default cache size? Can the cache size be based
on the computer? I don't mind giving apt lots of RAM on my desktop, but
my iPAQ doesn't have that much to give. I presume we just stay to
smaller package lists for smaller devices. That or proxy all the apt
stuff to a server :).
Can the memory problem be caught before it happens?
-- System Information
Debian Release: 3.0
Kernel: Linux fs 2.4.20-k6 #1 Sat Dec 21 17:26:12 EST 2002 i686
Locale: LANG=de_DE@euro, LC_CTYPE=
Versions of packages apt depends on:
ii libc6 2.2.5-11.2 GNU C Library: Shared libraries an
ii libstdc++2.10-glibc2.2 1:2.95.4-11woody1 The GNU stdc++ library