Solved!!!
Peter Lei of Cisco noticed this application uses mmap rather than
malloc so I could get what I wanted (go beyond 200 MB without ENOMEM)
if I adjusted sysctl -w vm.max_proc_mmap to be a higher value.
Thanks so much for everyone's help,
brad
On Fri, Feb 26, 2010 at 8:12 AM, Brad Penoff
Thanks Anton for the advice about a low kern.maxdsiz . Does that work
on your machine? I tried to give instructions in the original post so
that anyone can tune their machine and try to see what I am seeing.
Can others try to see on their own machines if the suggestions work?
I'll do anything to
On Thu, 25 Feb 2010 22:49:22 -0800, Brad Penoff wrote:
BP> I have a 32-bit machine with 2 GB running FreeBSD 8. I have a complex
BP> application that starts getting ENOMEM once the resident memory is
BP> about 200 MB. I adjusted the appropriate /boot/loader.conf and
BP> /etc/login.conf settings r
Greetings,
I have a 32-bit machine with 2 GB running FreeBSD 8. I have a complex
application that starts getting ENOMEM once the resident memory is
about 200 MB. I adjusted the appropriate /boot/loader.conf and
/etc/login.conf settings resulting in an increase in the "limit"
values to around 2 G
