Date: Mon, 16 May 2016 22:14:55 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 209512] mysql57-server-5.7.12: Server not usable after installation Message-ID: <bug-209512-13-6tcHrSOPsf@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-209512-13@https.bugs.freebsd.org/bugzilla/> References: <bug-209512-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209512 --- Comment #13 from Miroslav Lachman <000.fbsd@quip.cz> --- When and why it was changed? /usr/local/etc/my.cnf was there for a decade and I remember the problem (my= sql not starting after upgrade) with unintentional change in early versions of MariaDB port where /usr/local/etc/my.cnf was ignored. This is not expected result and thus it should be mentioned in UPDATING fil= e. I know it is displayed by rc script, but it doesn't help in automated environments. UPDATING is there for things like this. I also think that all mysql ports (mysql / mariadb / percona) should use the same config locations and similar rc scripts even if they are maintained by different persons. These ports should work as compatible replacements. For example MariaDB supports instances. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-209512-13-6tcHrSOPsf>