Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Not a Bug
-
10.3
-
None
Description
Reproduce
--source include/master-slave.inc
|
--source include/have_innodb.inc
|
|
|
connect (conn1,localhost,root,,test,$SLAVE_MYPORT,); |
select @@port; |
|
|
connect (conn2,localhost,root,,test,,$SLAVE_MYSOCK); |
select @@port; |
|
|
--echo Connecting client via -P
|
--exec echo "select @@port;" |$MYSQL -P $SLAVE_MYPORT test
|
|
|
--echo Connecting client via -S
|
--exec echo "select @@port;" |$MYSQL -S $SLAVE_MYSOCK test
|
|
|
--connection master
|
--source include/rpl_end.inc |
Result on Windows
connect conn1,localhost,root,,test,$SLAVE_MYPORT,; |
select @@port; |
@@port
|
16001
|
connect conn2,localhost,root,,test,,$SLAVE_MYSOCK; |
select @@port; |
@@port
|
16000
|
Connecting client via -P
|
@@port
|
16001
|
Connecting client via -S
|
@@port
|
16000
|
Result on Linux
connect conn1,localhost,root,,test,$SLAVE_MYPORT,; |
select @@port; |
@@port
|
16000
|
connect conn2,localhost,root,,test,,$SLAVE_MYSOCK; |
select @@port; |
@@port
|
16001
|
Connecting client via -P
|
@@port
|
16000
|
Connecting client via -S
|
@@port
|
16001
|
On Linux it works vice-versa: $SLAVE_MYPORT is incorrect and $SLAVE_MYSOCK is correct.
Expected
In all cases port 16001 returned or connection is failed with appropriate error message.