Hello,
I found that if you SHMALL value was less than your SHMMAX value,
the value wouldn't take.
J
Tom Lane wrote:
Qing Zhao <[EMAIL PROTECTED]> writes:
My suspision is that the change i made in /etc/rc does not take
effect.Is there a way to check it?
sysctl has an option to show the values
Qing Zhao <[EMAIL PROTECTED]> writes:
> My suspision is that the change i made in /etc/rc does not take
> effect.Is there a way to check it?
sysctl has an option to show the values currently in effect.
I believe that /etc/rc is the correct place to set shmmax on OSX 10.3 or
later ... but we have
Tom:
I used sysctl -A to see the kernel state, I got:
kern.sysv.shmmax: -1
It looks the value is too big!
Thanks!
Qing
On Apr 13, 2004, at 12:55 PM, Tom Lane wrote:
Qing Zhao <[EMAIL PROTECTED]> writes:
My suspision is that the change i made in /etc/rc does not take
effect.Is there a way to chec
On OS X, I've always made these changes in:
/System/Library/StartupItems/SystemTuning/SystemTuning
and manually checked it with sysctl after reboot. Works for me.
100k buffers is probably overkill. There can be a performance penalty with too many
buffers. See this lists' archives for more.
Hi, all,
I have got a new MaC OS G5 with 8GB RAM. So i tried to increase
the shmmax in Kernel so that I can take advantage of the RAM.
I searched the web and read the manual for PG7.4 chapter 16.5.1.
After that, I edited /etc/rc file:
sysctl -w kern.sysv.shmmax=4294967296 // byte
sysctl -w kern.sy