Just trying to do some triage. The reported bugs about mmap running out of room are for the following configurations: 195018 - oldstable + stable + unstable 380509 - stable + testing + unstable 385674 - oldstable + stable + testing 413024 - stable + testing + unstable 431410 - stable + testing + unstable 451526 - stable + testing + unstable + experimental 214666 - not specified 337831 - stable + testing 346136 - oldstable + stable + testing + unstable + experimental 359117 - stable + unstable + debian-marillat + third party repos 407078 - oldstable + stable + unstable I cannot reproduce #337831 getting the problem with just stable and testing. All others involve at least three distributions, but that's just not too unusual a thing to want to do. Why not: * Apply the trivial but very useful patch in #385674. The debian-user mailing list would thank you; we are asked about this FAQ weekly. * Increase the current hardcoded value to allow stable + testing + unstable ( + experimental? ) * Close all of the above bugs except #195018. Also, a thought: Since the bug seems to require not just a simple mremap but also support for relocating the pool, which I assume involves relocating pointers into the pool, maybe it's also time to consider some heuristic workarounds? For example, if there are more than 2 suites listed in sources.list, apt could use a Cache-Limit that is proportionally larger than the default. -- see shy jo
Attachment:
signature.asc
Description: Digital signature