Am 27.05.2011 11:45, schrieb Michael Schroeder: > On Thu, May 26, 2011 at 06:00:57PM +0300, Jonathan Dieter wrote: >> You're definitely right that applydeltarpm has a *far* lower memory >> footprint than createdeltarpm. But, looking at the original traceback, >> it looks like it isn't getting enough memory when it's trying to verify >> the sequence. > > Hmm, to me the traceback looks like the fork() system call in > yum failed, so applydeltarpm isn't even running. Additional info to yum/memory tonight on a virtual machine with 512 MB RAM yum-upgrade from fedora 13 to fedora 14, oom-killer played butcher while refreshing the kmod-open-vm-tools while depmod was running > Aktualisieren : gpac-devel-0.4.6-0.11.cvs20100527.fc14.x86_64 1093/2573 > Installieren : kmod-open-vm-tools-2.6.35.13-91.fc14.x86_64-0.0. 1094/2573 > bash: Zeile 1: 26878 Getötet yum -y upgrade 2>&1 "Getötet" = killed :-( even if this is not directly related to yum and kmod is an external package - depmod/update should not consume so much ressources because there are most services disabled and nothing running which needs more memory normally
Attachment:
signature.asc
Description: OpenPGP digital signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
