Comment 21 for bug 1571865
Revision history for this message
| Mohamed Hafez (mohamed-m-m-hafez) wrote | #21 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
So, if I understand correctly, after the upgrade, I'll still have a my.cnf file *exactly* as I left it, but the config file mysql will be using will be a my.cnf.migrated file, which will be a best-guess at auto-migrating my custom config. Is this correct?
After double-checking my.cnf.migrated and doing Workaround 3/3, can I just rename my.cnf.migrated to my.cnf and discard the old version, and be good to go?