Bug #36090 locked_in_memory as my.cnf parameter does not work
Submitted: 15 Apr 2008 12:06 Modified: 25 Apr 2008 22:08
Reporter: Oli Sennhauser Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.0.58 OS:Any
Assigned to: Paul Dubois CPU Architecture:Any

[15 Apr 2008 12:06] Oli Sennhauser
Description:
When we use the parameter locked_in_memory [ = 1 ] the mysqls server does not start.

How to repeat:
my.cnf

locked_in_memory = 1

or 

locked_in_memory

-->

080415 13:53:50  mysqld started
080415 13:53:50 [ERROR] /home/mysql/product/mysql-5.0.58/bin/mysqld: unknown option '--locked_in_memory'
080415 13:53:50  mysqld ended

Suggested fix:
Workaround:

Use memlock instead of locked_in_memory!

This is IMHO a bug or at least wrong in the docu.
[15 Apr 2008 13:31] MySQL Verification Team
Thank you for the bug report. Verified as described.
[25 Apr 2008 22:08] Paul Dubois
There is nothing to do here.  The description for locked_in_memory says:

Whether mysqld was locked in memory with --memlock.

So it's evident that the option to use is --memlock, not locked_in_memory.