From 20607c64ce768a8e226ec15c568b635e75406ef0 Mon Sep 17 00:00:00 2001 From: Guy Lichtman Date: Sat, 1 Jun 2013 02:19:08 -0700 Subject: [PATCH] Updated Configuration (markdown) --- Configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Configuration.md b/Configuration.md index d0eacda..80a1295 100644 --- a/Configuration.md +++ b/Configuration.md @@ -12,7 +12,7 @@ Available AUDIT Plugin system varaibles: * **audit_checksum**: Checksum for mysqld to validate (command line/conf file only). Used when audit_offsets are present. The plugin will not load if the specified checksum doesn't match the calculated one. This is useful when offsets have been set manually and you want to avoid using the manual offsets without validation after an upgrade of mysqld. * **audit_record_cmds**: Comma separated list of commands to log to the audit trail. For example: `insert,update,delete`. * **audit_record_objs**: Comma separated list of objects (tables) to log to the audit trail. Table name should be specified as: `database.table`. Wild cards are supported and it is possible to specify: `*.mytable` or `mydb.*`. -* **audit_whitelist_users**: Comma separated list of white-listed users whose queries are not to recorded. +* **audit_whitelist_users**: Comma separated list of white-listed users whose queries are not recorded. **Notes:** * When configuring boolean variables (enable/disable) in MySQL 5.1 via a configuration file (my.cnf) use 0/1 as values. For example: `audit_json_file=1`. There seems to be an issue with MySQL 5.1 where boolean configurations with `ON/OFF` values in my.cnf don't work.