James Pearson wrote:
> Ken Smith wrote:
>>
>> Hi James, brilliant "echo 3 > /proc/sys/vm/drop_caches" worked. So
>> does that mean that there wasn't enough free memory for yum to run?
>
> No, it might mean that there was a 'corruption' of the in-memory copy
> of 'something' used by yum/python
>
Ken Smith wrote:
>
> Hi James, brilliant "echo 3 > /proc/sys/vm/drop_caches" worked. So does
> that mean that there wasn't enough free memory for yum to run?
No, it might mean that there was a 'corruption' of the in-memory copy of
'something' used by yum/python
The above command flushes the fi
James Pearson wrote:
> Ken Smith wrote:
>
>> On both the faulty system and a good one, yum appears to hunt for
>> various versions of python files.
>>
>> Anyone with more knowledge than I have of system calls, is there a clue
>> in here?
>>
> You could try flushing the file system cache:
Ken Smith wrote:
>
> On both the faulty system and a good one, yum appears to hunt for
> various versions of python files.
>
> Anyone with more knowledge that I have of system calls, is there a clue
> in here?
You could try flushing the file system cache:
echo 3 > /proc/sys/vm/drop_caches
Reindl Harald wrote:
>
>
> Am 18.12.2012 19:41, schrieb Ken Smith:
>> Hi All, I have a Centos 5.8 system with relatively little memory, that
>> runs in rl3, where yum has decided not to work any more.
{snip}
>>
>> Any ideas where to look - I'm a bit stumped
>
> at least with "dmesg" and in /var/log
Hi All, I have a Centos 5.8 system with relatively little memory, that
runs in rl3, where yum has decided not to work any more. As follows:-
# free
total used free sharedbuffers cached
Mem:774628 697516 77112 0 77720 313284
6 matches
Mail list logo
