Date: Sat, 7 Aug 2010 17:00:19 GMT From: Robert Blayzor <rblayzor@inoc.net> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/149323: [libc] Applications with large memory footprint failing with mmap(2) - memory allocation errors Message-ID: <201008071700.o77H0JtE087283@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/149323; it has been noted by GNATS. From: Robert Blayzor <rblayzor@inoc.net> To: bug-followup@FreeBSD.org, rblayzor@inoc.net Cc: Subject: Re: kern/149323: [libc] Applications with large memory footprint failing with mmap(2) - memory allocation errors Date: Sat, 7 Aug 2010 12:37:27 -0400 Confirmed... After removing: kern.maxdsiz=3D"2048M" =46rom our /boot/loader.conf Our system has been functioning fine since. Our dcc server has been in = service for some time, since FreeBSD 4.x and has been upgraded to 6.x = and 7.x previously. It was not until we upgraded to 8.x (8.1 as = noticed) where we saw this problem. I am unaware if kern.maxdsiz is needed now, but I believe it was needed = at one time under 4.x as the kernel was killing the process after it = grew over 512MB. It does not seem to have that effect now... The = default maxdsiz in 8.x is still 512MB under i386, so it looks like the = behavior was changed between 7.x and 8.x. --=20 Robert Blayzor INOC, LLC rblayzor@inoc.net http://www.inoc.net/~rblayzor/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201008071700.o77H0JtE087283>