Hi Zhang,
on Tue, Nov 04, 2008 at 03:30:55PM +0800, you wrote:
I interpret the above as use a maximum of 300,000 KiB of memory, of
which 300 may be resident (i.e. in physical memory) and 299,700 swapped
out. That doesn't sound good, although I'm not sure I'm reading it
correctly.
Sorry,
Hello.
In my daily us of computer any process that takes more than 50% of the
memory (I read from top, not knowing if this is 50% of 384MB physical or
50% of having 800MB swap counted in) must have gone wrong, and usually
drag performance down to such extent that killing it is impossible
(because
Zhang Weiwu ha scritto:
So: is ulimit the solution? If so, what option should I set? My current
ulimit is:
$ ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) 30
scheduling priority (-e) 0
file size (blocks, -f) unlimited
Hi Zhang,
on Mon, Nov 03, 2008 at 06:24:00PM +0800, you wrote:
I hope I can configure the system so that any process uses more than 50%
of memory are automatically killed. first I was recommend to use ulimit
by googling around. However this seems doesn't work even if I set both
-d and -m (here
Matthias Bethke wrote:
Hi Zhang,
on Mon, Nov 03, 2008 at 06:24:00PM +0800, you wrote:
I hope I can configure the system so that any process uses more than 50%
of memory are automatically killed. first I was recommend to use ulimit
by googling around. However this seems doesn't work even if I
5 matches
Mail list logo
