On Sun, 24 Mar 2002, Alan Cox wrote:
> > > My system cannot (short of a bug) go OOM. Thats what the new overcommit
> > > mode 2/3 ensures
> >
> > How does a process react that doesn't get no more memory?
>
> Thats up to the process. If a program doesn't handle malloc/mmap/etc
> failures then its junk anyway
what's the point if you're just going to get signal delivery when you
least want it, even when malloc returns non-NULL? it could even be due to
stack growth which the compiler is under control of and has no exception
mechanism available. i personally prefer to take the signal and exit,
it's guaranteed to work in all cases. (hence, apache-1.3 and other
multiprocess daemon superiority over threaded and event-driven code, tee
hee :)
-dean
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Mar 31 2002 - 22:00:12 EST