On 5/17/06, rexonf <[EMAIL PROTECTED]> wrote:
Yeah, I can believe you. I read somewhere openbsd's stdlib free
actually frees up the memory unlike in Linux where you free it but it
sticks around hehe
True, but that's also a bit of a fib; according to free(3):
By default, Linux follows an optimistic memory allocation strategy.
This means that when malloc() returns non-NULL there is no guarantee
that the memory really is available. This is a really bad bug. In
case it turns out that the system is out of memory, one or more
processes will be killed by the infamous OOM killer. In case Linux
is employed under circumstances where it would be less desirable to
suddenly lose some randomly picked processes, and moreover the
kernel version is sufficiently recent, one can switch off this
overcommitting behavior using a command like
# echo 2 > /proc/sys/vm/overcommit_memory
See also the kernel Documentation directory, files vm/overcommit-
accounting and sysctl/vm.txt.
Cheers,
Zakame
--
Zak B. Elep || http://zakame.spunge.org
[EMAIL PROTECTED] || [EMAIL PROTECTED]
1486 7957 454D E529 E4F1 F75E 5787 B1FD FA53 851D
_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
[email protected] (#PLUG @ irc.free.net.ph)
Read the Guidelines: http://linux.org.ph/lists
Searchable Archives: http://archives.free.net.ph
