我lower_case_table_names = 2在/etc/my.cnf文件中设置。我还在/etc/mysql/my.cnf文件中更新了这个变量。设置变量后,我重新启动了 mysql 服务器,但当我使用SHOW VARIABLES.
我正在使用 MySQL 5.5。任何想法还需要做什么?
更新
my.cnf 内容:-
#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html
# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port = 3306
socket = /var/run/mysqld/mysqld.sock
# Here is entries for some specific programs
# The following values assume you have at least 32M ram
# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket = /var/run/mysqld/mysqld.sock
nice = 0
[mysqld]
#
# * Basic Settings
#
lower_case_table_names = 2
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
lc-messages-dir = /usr/share/mysql
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address = 127.0.0.1
#
# * Fine Tuning
#
key_buffer = 16M
max_allowed_packet = 16M
thread_stack = 192K
thread_cache_size = 8
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover = BACKUP
#max_connections = 100
#table_cache = 64
#thread_concurrency = 10
#
# * Query Cache Configuration
#
query_cache_limit = 1M
query_cache_size = 16M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
# As of 5.1 you can enable the log at runtime!
#general_log_file = /var/log/mysql/mysql.log
#general_log = 1
#
# Error log - should be very few entries.
#
log_error = /var/log/mysql/error.log
#
# Here you can see queries with especially long duration
#log_slow_queries = /var/log/mysql/mysql-slow.log
#long_query_time = 2
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
# other settings you may need to change.
#server-id = 1
#log_bin = /var/log/mysql/mysql-bin.log
expire_logs_days = 10
max_binlog_size = 100M
#binlog_do_db = include_database_name
#binlog_ignore_db = include_database_name
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
[mysql]
#no-auto-rehash # faster start of mysql but no tab completition
[isamchk]
key_buffer = 16M
#
# * IMPORTANT: Additional settings that can override those from this file!
# The files must end with '.cnf', otherwise they'll be ignored.
#
!includedir /etc/mysql/conf.d/
Run Code Online (Sandbox Code Playgroud)
正如您在文件中看到的,配置文件也被加载到多个位置。
!includedir /etc/mysql/conf.d/:检查此目录下的每个文件是否设置被覆盖:
grep -i lower_case_table_names /etc/mysql/conf.d/*
Run Code Online (Sandbox Code Playgroud)
或者手动检查文件并搜索配置值。
# - "~/.my.cnf" to set user-specific options.:检查.my.cnf运行守护进程的用户mysql,可能有这个设置被覆盖。
找出用户的 uid:
ps -ef | grep mysql
Run Code Online (Sandbox Code Playgroud)
第一行是 uid。使用以下命令查找用户的主目录:
grep <uid> /etc/passwd
Run Code Online (Sandbox Code Playgroud)
第 6 个:分隔的字符串是主目录。当此目录中有 a 时.my.cnf,将加载此文件。
使用 停止 mysql 守护进程/etc/init.d/mysql stop。并检查守护进程是否已通过pgrep mysql和停止pgrep mysqld。如果 pgrep 命令仍然返回 pid,则使用 杀死这些 pid kill。有时mysql需要很长时间才能停止处理庞大的数据库,这很正常。所以先等一下再杀东西。
如果您确定mysql已停止并且所有配置文件都已从此配置值中清除,则mysql重新启动/etc/init.d/mysql start并检查该值。
| 归档时间: |
|
| 查看次数: |
18225 次 |
| 最近记录: |