Bug #75407 | RFE - Modify init.d using --defaults-file | ||
---|---|---|---|
Submitted: | 5 Jan 2015 8:12 | Modified: | 5 Dec 2016 7:03 |
Reporter: | Javier Barroso | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Packaging | Severity: | S3 (Non-critical) |
Version: | 5.6 | OS: | Linux |
Assigned to: | Terje Røsten | CPU Architecture: | Any |
Tags: | init.d |
[5 Jan 2015 8:12]
Javier Barroso
[4 Dec 2016 22:11]
Terje Røsten
hi! > Why do you not use --defaults-file=my.cnf as parameter > (and remove get_mysql_option function) ? get_mysql_option is used to get specific *option* from the config file, --defaults-file just tells which config *file* to use. By adding --defaults-file="$conf" even if $conf=/etc/my.cnf is changing things. When --defaults-file is used, *only* this config file given will be used, without -defaults-file, several files will parsed and used, from my_print_default help text: Default options are read from the following files in the given order: /etc/my.cnf /etc/mysql/my.cnf /usr/etc/my.cnf ~/.my.cnf Any way, SysV initscripts is almost legacy these days, on platforms with systemd support, more advanced multi instance/flavour options are already available, see manual for a introduction: https://dev.mysql.com/doc/refman/5.7/en/using-systemd.html Here is example of such set up: http://thesubtlepath.com/blog/mysql/mysql-multi-instance-group-replication-on-systemd/ Is this good enough to cover your needs?
[4 Dec 2016 22:28]
Javier Barroso
Hello, Yes, with systemd this issue is obsolete. When I wrote this rfe I forgot about my.conf alternatives location. Thank you for take caring about PD: Please close this "bug"