--defaults-file unknown option even when first command line arg
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@
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_
./tmp/db.opt: No such file or directory
./log/db.opt: No such file or directory
./master-
./run/db.opt: No such file or directory
/home/jpipes/
/home/jpipes/
Error in my_thread_
Related branches
- Brian Aker: Pending requested
-
Diff: 47 lines (+17/-6)1 file modifieddrizzled/internal/default.cc (+17/-6)
Changed in drizzle: | |
status: | New → In Progress |
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...