Anaconda installs OOM with selinux-policy-targeted rpm from F9 updates
-----BEGIN PGP SIGNED MESSAGE-----
Martin Langhoff wrote:
> On Fri, Nov 7, 2008 at 9:49 AM, Daniel J Walsh <email@example.com> wrote:
>> selinux-policy-targeted is a memory hog, but it should not have changed
>> that drastically in updates.
>> Is this repeatable?
> 100% repeatable on the 3 attempts on the lower-mem machine. On the same machin
> The package selinux-policy-targeted 3.3.1 103.fc9 -- I am running a
> couple of additional installs to gather more information.
> On Fri, Nov 7, 2008 at 9:59 AM, Chris Lumens <firstname.lastname@example.org> wrote:
>>> - Anaconda OOMs without a warning or useful message to the user
>> I don't believe there's any way for anaconda to know this, and there's
>> certainly no way for us to do anything about it.
> Well, the behaviour is really weird. Perhaps there is no OOM killer in
> place during an anaconda install? If there was, it'd expect the rpm
> process or anaconda to be shot down -- but the machine is halting
> instead, it literally switches off.
> Whatever is bootstrapping anaconda (init script in the initrd?) should
> be able to at least see the odd exit status and echo a "something went
> wrong" msg...? Maybe that's the problem?
Well selinux-policy-targeted is not supported on olpc so you should
probably exclude it from the install. I can not imagine what in updates
caused it to grow. Upgrades add rules but usually not a large amount.
Going from Fedora 9 to 10 could be a problem.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
fedora-devel-list mailing list