Date: Sat, 26 Oct 1996 09:17:14 -0500 (CDT) From: Joe Greco <jgreco@execpc.com> To: hackers@freebsd.org Subject: HELP! :-( Hitting datasize limit Message-ID: <199610261417.JAA10206@earth.execpc.com>
next in thread | raw e-mail | index | archive | help
HELP! I have a very very large application: Usenet news (innd). I have been in the habit of starting it "unlimit"'ed for quite some time now. It starts off executing at about 55MB and will generally grow to double that within 12 hours. However, lately, it has been dying multiple times daily with malloc errors (using phkmalloc, but given the apparent cause I do not think this is the problem). The current situation would tend to have caused it to grow >> 110MB... and when I did a little looking into the problem, malloc was indeed returning NULL, which caused me to scratch my head until I typed "unlimit; limit"... cputime unlimited filesize unlimited datasize 131072 kbytes stacksize 65536 kbytes coredumpsize unlimited memoryuse unlimited descriptors 4136 memorylocked 251412 kbytes maxproc 2067 S***! 128MB absolute datasize limit on a process?!?! This machine has 256MB RAM and if INN wants to use it all, I really do not care. I can probably somehow hack a "raise" to this limit myself, but I have no idea what nasty side effects might be waiting for me and I am wondering what the idea or architectural reasons behind this "absolute" limit is. What is recommended in this case? ... JG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610261417.JAA10206>