Oliver Stahlhut wrote:
>
> Hello all!
>
> In the last months I had to "ALT-PRN-B"/reset many "almost dead" Linux
> numbercrunchers (kernel 2.2.[0-10], glibc2 based, >=512MB mem, 1GB Swap,
> 2 PentiumII) here in our cluster, who seem to have died because of
> memory mismanagement. If I start the following "wicked" ;) program twice
> (in parallel) any of our "better" machine crashes silently once the mem
> & swap are used up. If I start it on a 2.0.x machine, the job won't do
> any harm.
>
> Can anyone else reproduce my problem ... is it due to memory
> overcommitment ? - if yes, how can I turn it off ;)
>
I can reproduce it with only one program eating all memory. That why I asked
the memory allocation question over 2 month ago. I want to have hard limits
so that even requests for more memory lets say than MEM+SWAP-10MB (for kernel
and shells) are refused. Unfortunately I got no answer. But I think there is
no memory "accounting" at the moment
Cheers
Joachim
--
------------------------------------------------------------------------------
Joachim Gantenberg
------------------------------------------------------------------------------
Biomedizinische Technik | email : [EMAIL PROTECTED]
MA 4 / 55 | WWW : http://www.biomed.ruhr-uni-bochum.de/~ganti/
Ruhr-Uni-Bochum | tel : (+49) 234 700 6683
44780 Bochum / Germany | fax : (+49) 234 7094 117
------------------------------------------------------------------------------
-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
