-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Peter,
Peter Crowther wrote: | Which Linux, and have you disabled the kernel option that nukes the | largest process if the kernel can't allocate itself some memory? | Can't remember its name, but I know it's been mentioned previously on | this list. It's called the "OOM killer". From the GNU malloc man page: " 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 pro- cesses will be killed by the infamous OOM killer. In case Linux is employed under circumstances where it would be less desirable to sud- denly lose some randomly picked processes, and moreover the kernel ver- sion 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. " No work on what "sufficiently recent" means for kernel version, but I would guess that any 2.6 kernel or something after maybe 2.4.5 would be alright. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAke8fBYACgkQ9CaO5/Lv0PDRNwCffBn/N/+Eqz4QaonbhJYxWPvu LZAAoITWWp6+WQt6JU5IsAz0JwQQZXqM =e2GF -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
