github
/
mysql-audit
mirror of https://github.com/mcafee-enterprise/mysql-audit
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Updated Configuration (markdown)

master
Guy Lichtman 2013-06-01 02:19:08 -07:00
parent 1c5dafae6d
commit 20607c64ce
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
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_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_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_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:** **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. * 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.