From what I read you should only change kern.maxdsiz, changing
kern.dfldsiz makes every process allocating this amount of memory by
default, thats bad.
Something like:
kern.maxdsiz="1395864371" # 1.3GB
#kern.dfldsiz="1395864371" # 1.3GB
#kern.maxssiz="134217728" # 128MB
would do the trick for
On Jul 19, 2006, at 2:51 PM, Thaddeus Quintin wrote:
Or maybe it's trying to ask for a big shared memory segment...?
Your guess is as good as mine. Are there tools or anything else I
can use to try and figure this out?
MySQL probably has some documentation which would help, although if
you
On Jul 19, 2006, at 2:37 PM, Charles Swiger wrote:
On Jul 19, 2006, at 2:31 PM, Thaddeus Quintin wrote:
I already took care of that, it was in my first email-
I tweaked /boot/loader.conf to allow larger data size for
processes already (rebooted after changes)-
kern.maxdsiz="1395864371" # 1.3G
On Jul 19, 2006, at 2:31 PM, Thaddeus Quintin wrote:
I already took care of that, it was in my first email-
I tweaked /boot/loader.conf to allow larger data size for
processes already (rebooted after changes)-
kern.maxdsiz="1395864371" # 1.3GB
kern.dfldsiz="1395864371" # 1.3GB
kern.maxssiz="13
On Jul 19, 2006, at 1:38 PM, Charles Swiger wrote:
FreeBSD defaults to having a 512MB maximum process datasize. Add
something like:
kern.dfldsiz="1G"
...to /boot/loader.conf.
I already took care of that, it was in my first email-
I tweaked /boot/loader.conf to allow larger data siz
On Jul 19, 2006, at 1:14 PM, Thaddeus Quintin wrote:
The issue that I'm having is that when I start up MySQL I get a
couple "Out of Memory" errors before it actually starts up. Looks
like this-
060719 11:55:35 InnoDB: Started; log sequence number 0 43656
/usr/local/libexec/mysqld: Out of m