From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] oracle-mysql: check for my.cnf before starting
Date: Mon, 20 Aug 2018 20:23:26 +0200 [thread overview]
Message-ID: <20180820202326.26a15a07@windsurf> (raw)
In-Reply-To: <20180820111304.22933-4-chrismcc@gmail.com>
Hello,
On Mon, 20 Aug 2018 04:13:04 -0700, Christopher McCrory wrote:
> Signed-off-by: Christopher McCrory <chrismcc@gmail.com>
> ---
> package/oracle-mysql/S97mysqld | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/package/oracle-mysql/S97mysqld b/package/oracle-mysql/S97mysqld
> index 110ca2cd12..9777ff7775 100644
> --- a/package/oracle-mysql/S97mysqld
> +++ b/package/oracle-mysql/S97mysqld
> @@ -3,6 +3,7 @@
> MYSQL_DIR="/var/mysql"
> MYSQL_USER="mysql"
>
> +[ -r /etc/my.cnf ] || exit 0
Actually my preference is to fail hard if the configuration file
doesn't exist. I don't like those errors that are silently ignored, and
I've been lobbying to drop those test from our init scripts, and I
think most of the core contributors agreed with that.
If an /etc/my.cnf is mandatory for mysqld to start, then I would
suggest that we install an example/minimal /etc/my.cnf so that the
mysqld server starts properly in an out of the box Buildroot
installation.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-08-20 18:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 11:13 [Buildroot] [PATCH 0/3] oracle-mysql bugfix, security fix, and enhancement Christopher McCrory
2018-08-20 11:13 ` [Buildroot] [PATCH 1/3] oracle-mysql: fix hostname path Christopher McCrory
2018-08-20 18:21 ` Thomas Petazzoni
2018-08-20 11:13 ` [Buildroot] [PATCH 2/3] oracle-mysql: use group mysql, not nogroup Christopher McCrory
2018-08-20 18:21 ` Thomas Petazzoni
2018-08-20 11:13 ` [Buildroot] [PATCH 3/3] oracle-mysql: check for my.cnf before starting Christopher McCrory
2018-08-20 18:23 ` Thomas Petazzoni [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180820202326.26a15a07@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox