Date: Sat, 26 Oct 96 12:31:19 CDT From: Joe Greco <jgreco@solaria.sol.net> To: phk@critter.tfs.com (Poul-Henning Kamp) Cc: jgreco@ns.sol.net, hackers@FreeBSD.org Subject: Re: HELP! :-( Hitting datasize limit Message-ID: <199610261731.MAA08279@solaria.sol.net> In-Reply-To: <17119.846344098@critter.tfs.com> from "Poul-Henning Kamp" at Oct 26, 96 05:34:58 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> In message <199610261417.JAA10206@earth.execpc.com>, Joe Greco writes: > > >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"... > > You may want to > > ln -sf H /etc/malloc.conf > > I've not gotten a complete picture, but people indicate that it helps > a little bit. Hi Poul, I did not mean to imply that I think it has ANYTHING to do with phkmalloc... the growth in size is EXPECTED... innd allocates per-channel receive buffers. When the maximum allowed size for a Usenet article is 1MB and you have fifty inbound NNTP channels, it is reasonable to expect that the receive buffer for each channel will eventually need to be grown close to 1MB to allow for the large alt.binaries articles that everyone shovels around. I am sorry for any confusion. I simply was looking for a way to remove (or at least double) the datasize limitation. Thanks! :-) ... JG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610261731.MAA08279>