I'd have to say that things look fine in that regard.

core file size (blocks)     0
data seg size (kbytes)      unlimited
file size (blocks)          unlimited
max locked memory (kbytes)  unlimited
max memory size (kbytes)    unlimited
open files                  1024
pipe size (512 bytes)       8
stack size (kbytes)         8192
cpu time (seconds)          unlimited
max user processes          15231
virtual memory (kbytes)     unlimited

Heikki Tuuri wrote:

Hi!

We have only 2 GB of RAM in our SuSE Linux server, and I can allocate 1400
MB to the buffer pool.

Have you checked what

ulimit -a

says for the user running mysqld?

Best regards,

Heikki Tuuri
Innobase Oy
http://www.innodb.com
Foreign keys, transactions, and row level locking for MySQL
InnoDB Hot Backup - a hot backup tool for MySQL

Order MySQL technical support from https://order.mysql.com/


----- Original Message ----- From: ""Misaochankun"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Tuesday, August 26, 2003 4:01 AM
Subject: InnoDB can't use system's RAM as specified





I am coming across an annoying problem with a new InnoDB installation.
On a 4Gig RAM box, Mysql doesn't seem to want to grab the RAM I am
telling it to take.
I would like for it to try and use around 3 Gigs for its
innodb_buffer_pool_size, but it refuses to startup with anything greater
than 512M. I bugged RedHat about it, and they had me change the shared
memory allowance to 3Gigs, but nothing changed. I'd really like to get
the pool size up so that the server doesn't have to go to disk so often.
I will admit to being an InnoDB newbie, I am reading everything I can
find though and have used the example my.cnf files to tweak it pretty
decently. This memory issue is all that is really bugging me at the
moment.

*snip*







-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]



Reply via email to