Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!umich!samsung!sdd.hp.com!elroy.jpl.nasa.gov!ames!uhccux!munnari.oz.au!mel.dit.csiro.au!yarra!bohra!rod
From: rod@bohra.cpg.oz (Rod Bruce)
Newsgroups: comp.sys.ncr
Subject: Tower 32 - SHMBRK
Keywords: SHMBRK malloc sbrk
Message-ID: <396@bohra.cpg.oz>
Date: 11 Jul 90 04:55:48 GMT
Organization: Computer Power Group, Melb, Australia
Lines: 16

Under V.2 we can set the kernel parameter SHMBRK to specify the amount of space
that can be dynamically allocated before be bump up against any shared memory
segments.  We had to set a larger SHMBRK value on our machine so that our
program would not crash with a malloc failure.

Under V.3 however, the SHMBRK parameter does not exist (at least, I can't find
it anywhere) and so I was wondering -
	1. How does the system decide where to place shared memory segments?
	2. Can we run out of malloc space?
	3. Is there anything we can do to ensure that (2) does not happen?


Thanx in advance for your advice.
-- 
Rod Bruce, CP Software
rod@bohra.cpg.oz
D