You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

123 lines
3.3 KiB

mariadb: improve packaging and configuration At present there are some flaws related to configuration, also related to the packaging of mariadb. For starters there are complaints that the configuration is too static. To address this a new configuration layout is introduced. The primary configuration file (my.cnf) is changed so that it now only includes further configuration files in the directory /etc/mysql/conf.d. More default configuration files are added for the server and the client. This is the new default configuration. With these changes it's possible for the user to select if they want to change the default configuration (in conf.d/*.cnf) or if they want to drop their own files into conf.d instead. If the user .cnf files are read after the default .cnf files (files are included in alphabetical order), they will overwrite the settings from the default configuration. The other flaw is that the my.cnf file is included in mariadb-server. But that doesn't really fit the requirements, as the client also uses the configuration file(s). To accomodate this a new package mariadb-common is added. It installs the shared my.cnf file. The remaining changes add base packages, both for the server and the client. These are meant as foundation for the packages containing the respective binaries. In summary they will install the configuration, small miscellaneous files (SQL scripts etc.) and the user "mariadb". That means that everything is ready for the binaries, like mysql and mysqld. If there is not enough space left on flash memory, the user can just drop the binaries on a pendrive, link them to /usr/bin and get started. The ideas and configuration files were copied from Debian. Some amendments were made. Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
6 years ago
mariadb: improve packaging and configuration At present there are some flaws related to configuration, also related to the packaging of mariadb. For starters there are complaints that the configuration is too static. To address this a new configuration layout is introduced. The primary configuration file (my.cnf) is changed so that it now only includes further configuration files in the directory /etc/mysql/conf.d. More default configuration files are added for the server and the client. This is the new default configuration. With these changes it's possible for the user to select if they want to change the default configuration (in conf.d/*.cnf) or if they want to drop their own files into conf.d instead. If the user .cnf files are read after the default .cnf files (files are included in alphabetical order), they will overwrite the settings from the default configuration. The other flaw is that the my.cnf file is included in mariadb-server. But that doesn't really fit the requirements, as the client also uses the configuration file(s). To accomodate this a new package mariadb-common is added. It installs the shared my.cnf file. The remaining changes add base packages, both for the server and the client. These are meant as foundation for the packages containing the respective binaries. In summary they will install the configuration, small miscellaneous files (SQL scripts etc.) and the user "mariadb". That means that everything is ready for the binaries, like mysql and mysqld. If there is not enough space left on flash memory, the user can just drop the binaries on a pendrive, link them to /usr/bin and get started. The ideas and configuration files were copied from Debian. Some amendments were made. Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
6 years ago
mariadb: improve packaging and configuration At present there are some flaws related to configuration, also related to the packaging of mariadb. For starters there are complaints that the configuration is too static. To address this a new configuration layout is introduced. The primary configuration file (my.cnf) is changed so that it now only includes further configuration files in the directory /etc/mysql/conf.d. More default configuration files are added for the server and the client. This is the new default configuration. With these changes it's possible for the user to select if they want to change the default configuration (in conf.d/*.cnf) or if they want to drop their own files into conf.d instead. If the user .cnf files are read after the default .cnf files (files are included in alphabetical order), they will overwrite the settings from the default configuration. The other flaw is that the my.cnf file is included in mariadb-server. But that doesn't really fit the requirements, as the client also uses the configuration file(s). To accomodate this a new package mariadb-common is added. It installs the shared my.cnf file. The remaining changes add base packages, both for the server and the client. These are meant as foundation for the packages containing the respective binaries. In summary they will install the configuration, small miscellaneous files (SQL scripts etc.) and the user "mariadb". That means that everything is ready for the binaries, like mysql and mysqld. If there is not enough space left on flash memory, the user can just drop the binaries on a pendrive, link them to /usr/bin and get started. The ideas and configuration files were copied from Debian. Some amendments were made. Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
6 years ago
mariadb: improve packaging and configuration At present there are some flaws related to configuration, also related to the packaging of mariadb. For starters there are complaints that the configuration is too static. To address this a new configuration layout is introduced. The primary configuration file (my.cnf) is changed so that it now only includes further configuration files in the directory /etc/mysql/conf.d. More default configuration files are added for the server and the client. This is the new default configuration. With these changes it's possible for the user to select if they want to change the default configuration (in conf.d/*.cnf) or if they want to drop their own files into conf.d instead. If the user .cnf files are read after the default .cnf files (files are included in alphabetical order), they will overwrite the settings from the default configuration. The other flaw is that the my.cnf file is included in mariadb-server. But that doesn't really fit the requirements, as the client also uses the configuration file(s). To accomodate this a new package mariadb-common is added. It installs the shared my.cnf file. The remaining changes add base packages, both for the server and the client. These are meant as foundation for the packages containing the respective binaries. In summary they will install the configuration, small miscellaneous files (SQL scripts etc.) and the user "mariadb". That means that everything is ready for the binaries, like mysql and mysqld. If there is not enough space left on flash memory, the user can just drop the binaries on a pendrive, link them to /usr/bin and get started. The ideas and configuration files were copied from Debian. Some amendments were made. Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
6 years ago
  1. #
  2. # These groups are read by MariaDB server.
  3. # Use it for options that only the server (but not clients) should see
  4. #
  5. # See the examples of server my.cnf files in /usr/share/mysql/
  6. #
  7. # this is read by the standalone daemon and embedded servers
  8. [server]
  9. # this is only for the mysqld standalone daemon
  10. [mysqld]
  11. #
  12. # * Basic Settings
  13. #
  14. port = 3306
  15. # Don't put this on flash memory
  16. # datadir = /srv/mysql
  17. # tmpdir should also not go on flash memory, but needs to exist and have correct rights
  18. # tmpdir = /tmp
  19. skip-external-locking
  20. # Instead of skip-networking the default is now to listen only on
  21. # localhost which is more compatible and is not less secure.
  22. bind-address = 127.0.0.1
  23. #
  24. # * Fine Tuning
  25. #
  26. key_buffer_size = 16M
  27. max_allowed_packet = 16M
  28. thread_stack = 192K
  29. thread_cache_size = 8
  30. # This replaces the startup script and checks MyISAM tables if needed
  31. # the first time they are touched
  32. myisam_recover_options = BACKUP
  33. #max_connections = 100
  34. #table_cache = 64
  35. #thread_concurrency = 10
  36. #
  37. # * Query Cache Configuration
  38. #
  39. query_cache_limit = 1M
  40. query_cache_min_res_unit = 1k
  41. query_cache_size = 16M
  42. #
  43. # * Logging and Replication
  44. #
  45. # Be aware that this log type is a performance killer.
  46. # As of 5.1 you can enable the log at runtime!
  47. #general_log_file = /var/log/mysql/mysql.log
  48. #general_log = 1
  49. #
  50. # Error log - should be very few entries.
  51. # Note that if unset the errors will go to stdout and can be seen in syslog
  52. # (check "logread")
  53. #
  54. #log_error = /var/log/mysql/error.log
  55. #
  56. # Enable the slow query log to see queries with especially long duration
  57. #slow_query_log_file = /var/log/mysql/mariadb-slow.log
  58. #long_query_time = 10
  59. #log_slow_rate_limit = 1000
  60. #log_slow_verbosity = query_plan
  61. #
  62. #log-queries-not-using-indexes
  63. #
  64. # The following can be used as easy to replay backup logs or for replication.
  65. #server-id = 1
  66. #log_bin = /var/log/mysql/mysql-bin.log
  67. expire_logs_days = 10
  68. max_binlog_size = 100M
  69. #binlog_do_db = include_database_name
  70. #binlog_ignore_db = exclude_database_name
  71. #
  72. # * InnoDB
  73. #
  74. # InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
  75. # Read the manual for more InnoDB related options. There are many!
  76. innodb_file_per_table=1
  77. innodb_buffer_pool_size=64M
  78. innodb_flush_log_at_trx_commit=2
  79. innodb_log_buffer_size=32M
  80. innodb_max_dirty_pages_pct=90
  81. # You can set .._buffer_pool_size up to 50 - 80 %
  82. # of RAM but beware of setting memory usage too high
  83. #innodb_buffer_pool_size = 16M
  84. # Set .._log_file_size to 25 % of buffer pool size
  85. #innodb_log_file_size = 5M
  86. #innodb_log_buffer_size = 8M
  87. #innodb_flush_log_at_trx_commit = 1
  88. #innodb_lock_wait_timeout = 50
  89. #
  90. # * Security Features
  91. #
  92. # Read the manual, too, if you want chroot!
  93. # chroot = /var/lib/mysql/
  94. #
  95. # For generating SSL certificates you can use for example the GUI tool "tinyca".
  96. #
  97. # ssl-ca=/etc/mysql/cacert.pem
  98. # ssl-cert=/etc/mysql/server-cert.pem
  99. # ssl-key=/etc/mysql/server-key.pem
  100. #
  101. # Accept only connections using the latest and most secure TLS protocol version.
  102. # ..when MariaDB is compiled with OpenSSL:
  103. # ssl-cipher=TLSv1.2
  104. #
  105. # * Unix socket authentication plugin is built-in
  106. #
  107. # Needed so the root database user can authenticate without a password but
  108. # only when running as the unix root user.
  109. #
  110. # Also available for other users if required.
  111. # See https://mariadb.com/kb/en/unix_socket-authentication-plugin/