Oracle 5.0 Reference Manual page 428

Sets the
engine_condition_pushdown
Section 8.3.1.5, "Engine Condition Pushdown
This variable was added in MySQL 5.0.3.
•
--exit-info[=flags]
Command-Line Format
Option-File Format
This is a bit mask of different flags that you can use for debugging the
this option unless you know exactly what it does!
•
--external-locking
Command-Line Format
Option-File Format
Option Sets Variable
Disabled by
Enable external locking (system locking), which is disabled by default as of MySQL 4.0. Note that if
you use this option on a system on which
to deadlock. This option previously was named --enable-locking.
mysqld
External locking affects only
which it can and cannot be used, see
• [408]
--flush
Command-Line Format
Option-File Format
Variable Name
Variable Scope
Dynamic Variable
Flush (synchronize) all changes to disk after each SQL statement. Normally, MySQL does a write
of all changes to disk only after each SQL statement and lets the operating system handle the
synchronizing to disk. See
• [408]
--gdb
Server Command Options
Default
OFF
[449] system variable. For more information, see
Optimization".
[408],
-T [flags]
--exit-info[=flags]
-T [flags]
exit-info
Permitted Values
Type
numeric
[408]
--external-locking
external-locking
Yes,
skip_external_locking
skip-external-locking
Permitted Values
Type
boolean
Default
FALSE
does not fully work (such as Linux), it is easy for
lockd
table access. For more information, including conditions under
MyISAM
Section 8.7.4, "External
--flush
flush
flush
Global
Yes
Permitted Values
Type
boolean
Default
OFF
Section C.5.4.2, "What to Do If MySQL Keeps
408
server. Do not use
mysqld
[491]
Locking".
Crashing".