I had to use the --report-host argument in my environment and I couldn't seem to find it anywhere in conf.d/init.d, so I change them a bit. Here are the diffs.
Created attachment 85918 [details] /etc/conf.d/mysql diff
Created attachment 85919 [details] /etc/init.d/mysql diff
2 month and 2 days and no response. I bet other people are using master/slave mysql setups. I think they will benefit from this.
I do use a reasonably complex master/slave setup, but being an old hand at mysql, I don't use the report-host at all. It will however be considered for the next round of feature-set patches (Eg beyond the present series that need a GLSA coming soon for upstream issues).
Okay sounds really good to me. The more settings tweakable through conf.d the better. The reason for using the report host in my situation, is that I have several slaves together with the master. This is also useable if you have a redundant setup where the hostnames are the same, inside a vrrp setup, as an example.
Should I close this bug?
Sorry for the long delay. You should use the bash arrays in conf.d/mysql rather than adding more variables. Eg for your two cases: mysql_slot_0=( "report-host=slave0" ) mysql_slot_1=( "report-host=`hostname`" )
