On Thu, Nov 07, 2002 at 10:24:08AM -0700, Jason Gunthorpe wrote: > On Thu, 7 Nov 2002, Marius Gedminas wrote: > > > This cannot be fixed by increasing a magic value (I'm guessing > > APT:Cache-Limit) in apt.conf, because in the code the DynamicMMap > > constructor is never passed a WorkSpace argument and the default value > > of 2 MBytes is always used. > > Er it can and does work just fine. The command line option is '-o > APT::Cache-Limit=16777216' for instances.
You are absolutelty right. My mistake. Sorry. I tried "raising" it to 3 megs (thinking that the default was 2, as defined in apt-pkg/contrib/mmap.h), but actually the default was 6 (defined in apt-pkg/pkgcachegen.cc), and I needed 7. I also somehow managed to miss that 3 out of 4 constructor calls do pass the WorkSpace argument clear as day (only they call it MapSize instead and make the argument list parsing more difficult by having no spaces after commas, a convention I'm not used to). Now, where did I put that brown paper bag... Marius Gedminas -- What goes up, must come down. Ask any system administrator.
