drizzled not reading configuration file

[Lee Bieber]

On 10105 using upstart to start and stop drizzled, it is not reading the configuration file correctly.

% cat /etc/drizzle/drizzled.cnf
max-allowed-packet=67108864

% drizzle DATA_DICTIONARY
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Welcome to the Drizzle client.. Commands end with ; or \g.
Your Drizzle connection id is 1
Connection protocol: mysql
Server version: 2010.10.02 Debian

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
drizzle> select * from SESSION_VARIABLES where variable_name = 'max_allowed_packet';
+--------------------+----------------+
| VARIABLE_NAME | VARIABLE_VALUE |
+--------------------+----------------+
| max_allowed_packet | 1048576 |
+--------------------+----------------+
1 row in set (0 sec)

If I add the --max-allowed-package flag to the start script it works:

% drizzle DATA_DICTIONARY
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Welcome to the Drizzle client.. Commands end with ; or \g.
Your Drizzle connection id is 1
Connection protocol: mysql
Server version: 2010.10.02 Debian

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

drizzle> select * from SESSION_VARIABLES where variable_name = 'max_allowed_packet';
+--------------------+----------------+
| VARIABLE_NAME | VARIABLE_VALUE |
+--------------------+----------------+
| max_allowed_packet | 67108864 |
+--------------------+----------------+
1 row in set (0 sec)

[Andrew Hutchings (linuxjedi)]

Have you tried latest trunk? This should have been fixed since that build.

[Lee Bieber (kalebral-deactivatedaccount)]

yes, this is fixed with the latest from trunk