Re: Changing the location of my.ini and the order option files are read
Varuna, obviously it doesn't make much sense, to specify the my.ini location in my.ini itself. The --defaults-file option is used as a direct start-up parameter for mysql-server both, run as service or console-process. It simply tells the server-process where to look for the oneandonly my.ini. Any fullpath given here, overrides the default search-path during server-startup. I assume your server-process has been already started with a --defaults-file -option pointing to a my.ini in the mysql-application-directory, therefor it failed after deleting the file at this location. You may change the direct service-startup options by invoking mysqld-nt with options --remove and --install: With the install option you can specify the complete command-line including additional options which will be used when the server starts as a service. e.g. net stop mysql mysqld-nt --remove mysqld-nt --install MYSQL --defaults-file=\c:\program files(x86)\mysql\my.ini\ net start mysql Regards, Armin. 2008/10/6 Varuna Seneviratna [EMAIL PROTECTED]: I added a line to the [mysqld) group As --defaults-file=C:\WINDOWS\my.ini and then I restarted the service.Everything was fine.Then I took out the my.ini file in the MySQL instalation directory the result was an error message AS Could Not start the MySQL Service on Local Computer Error 1067 The preocess terminated unexpectedly According to the manual MySQL server reads option files in the order Default options are read from the following files in the given order: C:\WINDOWS\my.ini C:\WINDOWS\my.cnf C:\my.ini C:\my.cnf C:\Program Files\MySQL\MySQL Server 5.0\my.ini C:\Program Files\MySQL\MySQL Server 5.0\my.cnf To see the order I ran the command mysqld-nt --verbose --help If the optin files read order is as above why can,t get the service started Varuna -- Aegaeon technologies GmbH phone: +49.941.8107344 fax: +49.941.8107356 Legal disclaimer: http://aegaeon.de/disclaimer/email_all_int.txt -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
mysqldnt 3.23.36 (WIN32) crashed after ALTER TABLE DROP COLUMN
From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject:table modification [ALTER TABLE DROP COLUMN name]; on large table (1.7gb) crashed mysqldnt Description:- attempt to extract a longblob column from a large table with ca. 200.000 records into a separate table (successful) - dropping the blob_column from the large table (success) consecutive access to the database by an odbc-client caused the server to crash. stack_trace (dump.txt) attached How-To-Repeat: bug has been reproduced a 2nd time by dropping another column from the same table. Actually, the original table is not available anymore, because the crash corrupted the indexfile. Further attempts to reproduce the failure on backup-tables in progress. Fix:none so far Synopsis: mysqldnt crashed after ALTER TABLE DROP COLUMN Submitter-Id: ASC Originator: Armin Schöffmann Organization: Aegaeon technologies GmbH MySQL support: licence Severity: critical Priority: Category: mysqld Class: sw-bug Release:mysql-3.23.36 Exectutable:mysqld Environment:Dell Optiplex, Intel PIII, 256mb, nt5sp1(us)ws System: Win2000 Compiler: VC++ 6.0 Architecture: i686 Aegaeon technolgies GmbH Stadtamhof 15 93059 Regensburg Germany fon:+49.941.8107344 fax:+49.941.8107356 www.aegaeon.de - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
