Re: apt emite erro apos update: como resolve-lo?

[Tiago Saboga <tiagosaboga@terra.com.br>]

Em Sáb 08 Out 2005 17:54, Marcelo Luiz de Laia escreveu:
> Dynamic MMap ran out of room

Procurando no google por essa mensagem de erro você encontrará centenas de 
pessoas que já tiveram o mesmo problema... Transcrevo abaixo a mensagem que 
achei mais interessante a respeito, apesar de ser em inglês...

Resumindo, leia a página de manual do apt.conf, e altere o tamanho limite do 
cache...

[]s,

tiago.


> de:
> http://lists.samba.org/archive/linux/2004-February/009792.html
> 
> I got this the other day
> 
> Reason for problem: apt allocates a static sized block of memory and if
> the packages and release files it downloads from the sources.list exceed
> that memory, kaput bang - you get what you see there. 
> 
> Simple solution: comment out a few lines in your sources.list and try
> again
> 
> 'Better' solution: check out `man apt.conf` and look for the
> 'Cache-Limit options
> 
> 
> When I first saw this I considered it a bug - shoulnd't your package
> management program be SUPER robust? and besides, having a static memory
> size like that assumes a level of knowing the maximum possible size of
> the next debian release...
> 
> However, having it allocate memory dynamically as needed could be a
> security risk - do you really trust a file on a remote site to determine
> memory usage on your local machine? (try gzipping a few gig of null's to
> get an idea of how a malicious packages.gz file could hurt ;)
> 
> er, I think that's answered for you now? :)
> 
> (PS: make sure you have the latest apt-get - the default limit has
> probably been increased since the version you have anyways, due to
> exactly this ;)
> 
> .../Nemo