1

As per title. In /etc/mysql/my.cnf I see:

!includedir /etc/mysql/conf.d/
!includedir /etc/mysql/mysql.conf.d/

.cnf files from both location are loaded: why having two? Which one is the "right one" for my own .cnf?

  • This belongs in dba.stackexchange.com . – Rick James Feb 17 at 3:52
2

Both are global options. In this case,

!includedir /etc/mysql/mysql.conf.d/

is an SYSCONFDIR generate by ubuntu when Mysql was compiling for the package in CMAKE option.

More info https://dev.mysql.com/doc/refman/8.0/en/option-files.html

  • 1
    Thanks for your reply. So I understand that /etc/mysql/mysql.conf.d is there just for retrocompatibility and /etc/mysql/conf.d is the way to go, right? – Dr. Gianluigi Zane Zanettini Feb 16 at 23:11
  • 1
    Yes, it's right. – Pserr Feb 17 at 18:52

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.