On 02/13/2013 12:34 PM, Honza Horak wrote:
On 02/12/2013 09:10 PM, Sergei Golubchik wrote:
> Okay, so you suggest to do nothing - neither append the includedir line
> to the existing my.cnf nor let mariadb read /etc/my.cnf.d/ automatically
> and implicitly.
> That's fine :)
> I was only trying to find an alternative to "let mariadb read
> /etc/my.cnf.d implicitly" - because I don't like an idea of adding more
> magic to the server, it has more than enough of it already.
Going back to the original idea -- it was that users will be confused
if they'll see files under /etc/my.cnf.d/* which they can enhance but
it won't take any effect. Well, adding a README file into
/etc/my.cnf.d or some comments into files in that directory or even
both, that would simply describe the need of !includedir, should just
work. That shouldn't do any harm and should reduce confusing.
Is not the correct course here that mariadb comes with it's own mdb.cf
file and it's own mdb.d directory?
Surely you are not honestly consider replacing mysql installation with
mariadb on upgrades?
I for one would not want to find out that my mysql install would have
been replaced with mariadb on upgrade ( or visa versa )