On Wed, 2005-09-07 at 21:43 +0200, Maciej ?enczykowski wrote: > Ok, that _CANNOT_ be yum's problem, some other part of your system is > flaky. Either Hard Disk, or HDD drivers, or RAM, or CPU, or kernel > drivers for one of the above. But it is _NOT_ yum. It can't be. Yum may > be the most likely to trigger it, but that doesn't make it it's problem. Yum does some very CPU and disk intensive operations ... which can make things like bad memory, overloaded power supplies, bad cooling fans, etc. have an effect. I agree with Maciej .. I don't see how yum could, by itself, cause a hard freeze. > It just isn't possible (no program can freeze the machine under linux, if > a program does freeze the machine, then either there's a bug in the > kernel, a hardware error or the program is running with ioport priveledges > (which yum doesn't use)). Again, try running memtest86 and mprime on it - > verify that the systems CPU and RAM are stable, then try running some disk > intensive tasks, then try running them concurrent to mprime. But it's > 99.99% guaranteed that you either have flaky hardware or flaky kernel > drivers. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.centos.org/pipermail/centos/attachments/20050907/fa692ade/attachment.bin