MySQL Bugs: #2722: Points to incorrect data folder

Bug #2722	Points to incorrect data folder
Submitted:	11 Feb 2004 22:11	Modified:	10 Mar 2004 15:03
Reporter:	Charles Johnson	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S2 (Serious)
Version:	1.0.1aALPHA	OS:	Windows (WindowsXP Pro)
Assigned to:	Ulrich Bayer	CPU Architecture:	Any

Description:
I am using a my.ini file that points to d:\data.  However, MySQL Administrator points to C:/MySQL/data

Below this line I am pasting my my.ini file.

CAVEAT: I AM A NEWBIE!!!

***************************************************************************

# Example mysql config file.
# Copy this file to c:\my.cnf to set global options
# 
# One can use all long options that the program supports.
# Run the program with --help to get a list of available options

# This will be passed to all mysql clients
[client]
#password=my_password
port=3306
#socket=MySQL

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

# The MySQL server
[mysqld]
port=3306
#socket=MySQL
skip-locking
set-variable	= key_buffer=16K
set-variable	= max_allowed_packet=1M
set-variable	= thread_stack=64K
set-variable	= table_cache=4
set-variable	= sort_buffer=64K
set-variable	= net_buffer_length=2K
server-id	= 1

# Uncomment the following if you want to log updates
#log-bin

# Uncomment the following rows if you move the MySQL distribution to another
# location
basedir = c:/mysql/
datadir = d:/data/

# Uncomment the following if you are NOT using BDB tables
#skip-bdb

# Uncomment the following if you are using Innobase tables
#innodb_data_file_path = ibdata1:100M
#innodb_data_home_dir = c:\ibdata
#innodb_log_group_home_dir = c:\iblogs
#innodb_log_arch_dir = c:\iblogs
#set-variable = innodb_mirrored_log_groups=1
#set-variable = innodb_log_files_in_group=3
#set-variable = innodb_log_file_size=5M
#set-variable = innodb_log_buffer_size=8M
#innodb_flush_log_at_trx_commit=1
#innodb_log_archive=0
#set-variable = innodb_buffer_pool_size=16M
#set-variable = innodb_additional_mem_pool_size=2M
#set-variable = innodb_file_io_threads=4
#set-variable = innodb_lock_wait_timeout=50

[mysqldump]
quick
set-variable	= max_allowed_packet=16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

#Path to the database root
datadir=d:/MySQL/data

[isamchk]
set-variable	= key_buffer=8M
set-variable	= sort_buffer=8M

[myisamchk]
set-variable	= key_buffer=8M
set-variable	= sort_buffer=8M

[mysqlhotcopy]
interactive-timeout

How to repeat:
Not sure

Suggested fix:
No idea

With Windows XP SP1, under "Service Control" -> "Configure Service" tab -> "Configuration File" fieldset, "Config Filename" shows "C:\WINDOWS\\my.ini" when it should be "C:\WINDOWS\my.ini" (not double the \ like \\) and in the same fieldset, "Section Name" has value of "Files/MySQL/bin/mysqld-nt.exe" which should be "C:/Program Files/MySQL/bin/mysqld-nt.exe".

By the way, this last value is greyed, can't be changed.

Let me know if this requires it's own bug filling.

Forgot to mention, in that same window, under the "Server Features" fieldset, the entry "Path to binary:" has the value "C:/Program" which is shown in a red font. Clicking on the browser button that follows it doesn't open a browsing window.

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Hi,

Sorry for taking so long. We have changed the startup-variables thing a bit and recoded some parts. As a consequence this bug should be gone too. The new binary release should be available in the next days with many bugs fixed and some new features.