Oracle 5.0 Reference Manual page 435

• [415]
--memlock
Command-Line Format
Option-File Format
Variable Name
Variable Scope
Dynamic Variable
Lock the process in memory. This option might help if you have a problem where the
mysqld
operating system is causing
[415] works on systems that support the
--memlock
Solaris, most Linux distributions that use a 2.4 or newer kernel, and perhaps other Unix systems.
On Linux systems, you can tell whether or not
checking to see whether or not it is defined in the system
shell> grep mlockall /usr/include/sys/mman.h
If is supported, you should see in the output of the previous command something like
mlockall()
the following:
extern int mlockall (int __flags) __THROW;
Important
Use of this option may require you to run the server as root, which, for
reasons of security, is normally not a good idea. See
Run MySQL as a Normal
On Linux and perhaps other systems, you can avoid the need to run the
server as
the memlock limit in
You must not try to use this option on a system that does not support the
mlockall()
as you try to start it.
•
--myisam-block-size=N
Command-Line Format
Option-File Format
The block size to be used for
•
--myisam-recover[=option[,option]...]]
Command-Line Format
Option-File Format
Server Command Options
--memlock
memlock
locked_in_memory
Global
No
Permitted Values
Type
boolean
Default
FALSE
to swap to disk.
mysqld
mlockall()
User".
by changing the
root limits.conf
Section 8.9.7, "Enabling Large Page
system call; if you do so,
[415]
--myisam-block-size=#
myisam-block-size
Permitted Values
Type
numeric
Default
1024
Range
1024 .. 16384
index pages.
MyISAM
--myisam-recover[=name]
415
myisam-recover
system call; this includes
mlockall()
(and thus this option) is supported by
file, like this:
mman.h
Section 6.1.5, "How to
file. See the notes regarding
Support".
will very likely crash as soon
mysqld
[415]