On Fri, 6 Jul 2001, Haim Gelfenbeyn wrote:
> I don't think this is VM problem... Look more like misbehaved program
> running as root which allocates more and more memory .VM starts killing
> processes when some resource gets scarse (I don't remember if it's CPU
> time or virtual memory). Maybe you should look at sysstat, it will log
> CPU and memory useage, and you will find what process goes out of hand
> when it happens next time.
>
> Haim.
Where can I find this 'sysstat'?
On Fri, 6 Jul 2001, mulix wrote:
> your machine is running out of memory, and the VM is trying to kill the
> processes responsible for it (without much success, it appears). you can
> do one of several things:
>
> * check which process is behaving badly, and ulimit(1) it in advance.
How can I know which process it is? Can a non-root porcess be the cause of
this as well?
> * upgrade to the latest kernel (2.4.6) and hope the VM heuristics are
> better, so it only kills the offending process.
I'm currently using kernel 2.2.17, do you know that the VM heuristics are
in-fact improved?
> * add more swap (no need to make a swap partition, you can use a swap
> file).
I have 192M of RAM and 128M of sawp, is this enough?
On Fri, 6 Jul 2001, Dani Arbel wrote:
> Alon,
> If you are using a 2.4 kernel prior to 2.4.5 then you are a victim of its
> VM problem. Upgrade to 2.4.5 .
> Dani
Does this mean that 2.2 kernels don't have this problem?
Thanks all for your help,
Alon
--
This message was sent by Alon Altman ([EMAIL PROTECTED]) ICQ:1366540
The RIGHT way to contact me is by e-mail. I am otherwise nonexistent :)
--------------------------------------------------------------------------
The last time I saw him he was walking down Lover's Lane holding his own hand.
-- Fred Allen
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
