Got it!
No need to rebuild, just tune those kernel params and reboot.
Look at..
/sbin/sysconfig -q proc
/sbin/sysconfig -q vm
vm-maxvas sets a hard limit to the address space so setting
max-per-proc-address-space to something larger will cause
unlimit to report that it can't reach the requested size.
There are, I'm told, many such kernel parameter dependencies but
no obvious documentation.
So...
If you are in a similar situation to myself you may want to...
set vm-maxvas = RAM + swap
set max-per-proc-address-space = vm-maxvas - some room for system
set per-proc-address-space = RAM
I have only guessed at this but it seems to work.
I'm sure that there are reasons to choose other strategies for
other application fields. I guess this is where the real art
of the sysop is required. Me.. I'm just a sad old fortran
hacker ;-)
Tally ho!
k.mcmanus_at_gre.ac.uk -
http://www.gre.ac.uk/~k.mcmanus
-------------------------------------------------------------
Dr Kevin McManus ||
School of Computing & Math Science ||
The University of Greenwich ||
Wellington St. Woolwich ||Tel +44 (0)181 331 8719
London SE18 6PF UK ||Fax +44 (0)181 331 8665
Received on Fri May 28 1999 - 09:12:43 NZST