I know FreeBSD 4.x is old..., but we are using on a production system
with postgres and apache. The above message
is appearing periodically. I googled for the message but found no
recommendation for adjusting it.
Is the sysctl kern.vm.pmap.shpgperproc available on 4.x? This can be
configured
Hello List,
I know FreeBSD 4.x is old..., but we are using on a production system
with postgres and apache. The above message
is appearing periodically. I googled for the message but found no
recommendation for adjusting it.
Any suggestions.
Thanks,
Steve
--
They that give up essential
Stephen Clark wrote:
Claus Guttesen wrote:
Stephen Clark wrote:
I know FreeBSD 4.x is old..., but we are using on a production system
with postgres and apache. The above message
is appearing periodically. I googled for the message but found no
recommendation for adjusting it.
Is the sysctl
Hi Steve,
Stephen Clark wrote:
Uwe Doering wrote:
[...]
But you can put that option into the kernel config file:
options PMAP_SHPGPERPROC=...
and build a new kernel with it.
You are correct. My question is more how much should I increase it. The
current default in the 4.x LINT file
is
But you can put that option into the kernel config file:
options PMAP_SHPGPERPROC=...
and build a new kernel with it.
You are correct. My question is more how much should I increase it. The
current default in the 4.x LINT file
is options PMAP_SHPGPERPROC=201 should I double it?
Claus Guttesen wrote:
I know FreeBSD 4.x is old..., but we are using on a production system
with postgres and apache. The above message
is appearing periodically. I googled for the message but found no
recommendation for adjusting it.
Is the sysctl kern.vm.pmap.shpgperproc available on
Uwe Doering wrote:
Hi Steve,
Stephen Clark wrote:
Uwe Doering wrote:
[...]
But you can put that option into the kernel config file:
options PMAP_SHPGPERPROC=...
and build a new kernel with it.
You are correct. My question is more how much should I increase it.
The current default