mariadb/mysql-test/suite/binlog_encryption/my.cnf
Sergei Golubchik d7699c51eb test.cnf files should !include default_my.cnf
not default_mysqld.cnf. The latter has only server settings,
it misses mtr-specific client configuration

Except for spider, that doesn't use mysqld.1 server
and default_my.cnf starts it automatically.
Spider tests have to include both default_mysqld.cnf and
default_client.cnf
2024-02-03 11:22:20 +01:00

26 lines
592 B
INI

!include include/default_my.cnf
[mysqld.1]
innodb
plugin-load-add= @ENV.FILE_KEY_MANAGEMENT_SO
loose-file-key-management-filename= @ENV.MYSQLTEST_VARDIR/std_data/keys.txt
encrypt-binlog
log-basename= master
[mysqld.2]
#!use-slave-opt
innodb
log-slave-updates
log-basename= slave
[ENV]
# We will adopt tests with master-slave setup as well as rpl_init setup,
# so need both sets of variables
MASTER_MYPORT= @mysqld.1.port
SERVER_MYPORT_1= @mysqld.1.port
SERVER_MYSOCK_1= @mysqld.1.socket
SLAVE_MYPORT= @mysqld.2.port
SERVER_MYPORT_2= @mysqld.2.port
SERVER_MYSOCK_2= @mysqld.2.socket