Out of memory errors when not out of memory ... what to do for OSF 4.0

[Gareth Pearce]

Hi,
I failed to find a gants report for this before... and now have discovered 
the solution to the cause of mmap returning out of memory, when plainly the 
system isnt out of memory, on OSF alpha 4.0
The problem is (seems to be) that OSF has system limits predefined at a far 
too low level, for a number of vm parameters.  including a maximum of 200 
mem-maps per process.
A system utility called sys_check is available which recommends 
modifications to theses values - ~16000 in the case of memmap's.
(without this change, mmap has to be disabled in autohost.h in order to 
boostrap)
I was wondering if a) someone might know of an appropriate gnats report - 
which could have a comment appended (if it doesnt already, since I couldnt 
find one), and/or if b) prehaps a small check could be added to configure 
for OSF/1 alpha to display a warning saying that their mmap limit is too 
low, if it is.

Regards,
Gareth

_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx