VM: killing process X

V13 v13 at priest.com
Fri May 28 21:24:30 EEST 2004


On Friday 28 May 2004 16:44, Christos Ricudis wrote:
> To senario einai poly syxnotero apo oti fantazesai. Me opoiadhpote logikh
> kai na prospa8hseis na dialekseis TI 8a skotwseis, exeis megalh pi8anothta
> na skotwseis kapoio entelws asxeto process.
>
> O monos algori8mos poy douleyei einai o ekshs :

[...]

Yparxei kai allos enas akoma poio aplos algorithmos...

apo to man page tis malloc :):

-----
void *malloc(size_t size);

       For calloc() and malloc(), the value returned is a pointer
       to the allocated memory, which is suitably aligned for any
       kind of variable, or NULL if the request fails.
-----

Opote to mono poy menei einai o kernel na min kanei tipote oste opoiodipote 
programma elegxei to apotelesma ton malloc() poy kanei na min kindinevei na 
skotothei (Ta ypoloipa tha trone sigsegv)... To mono poy xreiazetai einai ena 
echo 1 > /proc/sys/vm/overcommit_memory
h 
echo 2 > /proc/sys/vm/overcommit_memory

Apla epidi ayto den to kanei sxedon kanenas (including me), yparxei (ypirxe) o 
oom killer... Tora, to oti kindinevei na soy skotosei ton sshd kai na 
s'afisei ekso apo to mixanima, einai ena allo thema.

> 6) Nothing of the above? Question the user WHAT the heck is running other
> than these that COULD EVER CAUSE a OOM condition even in a 32mb VM
> environment.

Opos eipes, 'question the user'... anakrisi me lampa klp klp

<<V13>>




More information about the Linux-greek-users mailing list