--defaults-file unknown option even when first command line arg

Bug #552936 reported by Jay Pipes
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Drizzle
Fix Released
Medium
Monty Taylor
Cherry
Fix Released
Medium
Monty Taylor

Bug Description

Title says it all. I can't test startup options properly until this is resolved...

Here is output of starting up a drizzled instance with --defaults-file as the first arg and to a correct and proper config file

jpipes@serialcoder:~/repos/drizzle/replication-channel-id/tests$ /home/jpipes/repos/drizzle/replication-channel-id/drizzled/drizzled --defaults-file=/home/jpipes/repos/drizzle/replication-channel-id/plugin/transaction_log/tests/include/startup_variables.cnf --mysql_protocol_port=9306 --basedir=/home/jpipes/repos/drizzle/replication-channel-id/ --drizzle_protocol_port=9307 --datadir=/home/jpipes/repos/drizzle/replication-channel-id/tests/var
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins.
100331 19:35:13 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
100331 19:35:13 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
100331 19:35:14 InnoDB Plugin 1.0.4 started; log sequence number 44264
./std_data_ln/db.opt: No such file or directory
./tmp/db.opt: No such file or directory
./log/db.opt: No such file or directory
./master-data/db.opt: No such file or directory
./run/db.opt: No such file or directory
/home/jpipes/repos/drizzle/replication-channel-id/drizzled/drizzled: unknown variable 'defaults-file=/home/jpipes/repos/drizzle/replication-channel-id/plugin/transaction_log/tests/include/startup_variables.cnf'Aborting
/home/jpipes/repos/drizzle/replication-channel-id/drizzled/drizzled: Shutdown complete
Error in my_thread_global_end(): 1 threads didn't exit

Related branches

Revision history for this message
Jay Pipes (jaypipes) wrote :

Note the:

Error in my_thread_global_end(): 1 threads didn't exit

Causes problems in test suite because of the above....took me a while to track it down...

Monty Taylor (mordred)
Changed in drizzle:
status: New → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.