[MDEV-4509] mysql init script should accept arguments Created: 2013-05-10  Updated: 2014-03-04  Resolved: 2013-06-13

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 10.0.2, 5.5.30, 5.5.29-galera
Fix Version/s: 10.0.4, 5.5.32

Type: Bug Priority: Major
Reporter: Kolbe Kegel (Inactive) Assignee: Sergei Golubchik
Resolution: Fixed Votes: 1
Labels: None
Environment:

Debian, Ubuntu

Issue Links:
Duplicate
duplicates MDEV-4253 service mysql start --wsrep-cluster-a... Closed
duplicates MDEV-4508 Ubuntu (possible debian) /etc/init.d/... Closed
Relates
relates to MDEV-4253 service mysql start --wsrep-cluster-a... Closed

 Description   

The /etc/init.d/mysql script does not accept any arguments, even though the "service" tool on those platforms does accept arguments/"OPTIONS" these days. This is particularly problematic in the case of Galera, for example, where you may occasionally need to pass --wsrep-cluster-address=gcomm:// to bootstrap a cluster.

This issue is very easily resolved by replacing this line:

            /usr/bin/mysqld_safe > /dev/null 2>&1 &

with this one:

            /usr/bin/mysqld_safe "${@:2}" > /dev/null 2>&1 &



 Comments   
Comment by Tomas Gustavsson [ 2013-05-11 ]

I believe MDEV-4253 is the same issue, the analysis there is the same, i.e. mysql init script does not pass on parameters.

Comment by Tomas Gustavsson [ 2013-05-14 ]

Verified that the patch with:

/usr/bin/mysqld_safe "${@:2}" > /dev/null 2>&1 &

works fine.
Now:
service mysql start --wsrep-cluster-address=gcomm://

works great.

Comment by Elena Stepanova [ 2013-05-22 ]

Not really sure who it should belong to, please reassign if needed.

It's more generic than MDEV-4253 and I also don't see why not to do it in all init scripts rather than Galera only; but I'm inclined to keep MDEV-4253 open too, and assigned to Seppo, so that he'll make the change in the upstream (codership) version of the script and it won't get lost on the next merge if it again comes as a replacement of the old files.

Comment by Elena Stepanova [ 2013-06-11 ]

Raising the priority due to upcoming 5.5.31-galera release, since it should be easy and safe to fix.
See also MDEV-4253.

Comment by Daniel Black [ 2014-03-04 ]

seems to be fixed
mariadb-galera-server-5.5 5.5.35+maria-1~wheezy

 fgrep safe /etc/init.d/mysql
 
 
 
#                    and its wrapper script "mysqld_safe".
 
            /usr/bin/mysqld_safe "${@:2}" > /dev/null 2>&1 &

Generated at Thu Feb 08 06:56:59 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.