I'd like to connect to a remote MySQL server via stunnel.
Unfortunatelly, the most reasonable way, i.e. connection to localhost, does not work. It sounds strange, but the parameter
host = localhost
involve connecting through /var/run/mysql/mysql.sock,
despite of value of the 'port' parameter.
So, is there any way to force nss_mysql to connect
to <port>:localhost?
(And, BTW, is this 'bug or feature'?)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Till now I used to use an address of the net interface. It's an clumsy solution in an environment based on dhcp. Local loopback would by much comfortable.
So, this is the intendent feature?
Is it uchnageable? Or, there a chance to work around?
(BTW, maybe stunnel can read a socket? I couldn't force it to do this.)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'd like to connect to a remote MySQL server via stunnel.
Unfortunatelly, the most reasonable way, i.e. connection to localhost, does not work. It sounds strange, but the parameter
host = localhost
involve connecting through /var/run/mysql/mysql.sock,
despite of value of the 'port' parameter.
So, is there any way to force nss_mysql to connect
to <port>:localhost?
(And, BTW, is this 'bug or feature'?)
Hey,
please take a look to the docs..
http://libnss-mysql.sourceforge.net/configuration.shtml#connectivity
says:
port Integer client default TCP/IP port of MySQL server (fi host is not localhost)
Oh! Yes. Indeed.
Till now I used to use an address of the net interface. It's an clumsy solution in an environment based on dhcp. Local loopback would by much comfortable.
So, this is the intendent feature?
Is it uchnageable? Or, there a chance to work around?
(BTW, maybe stunnel can read a socket? I couldn't force it to do this.)