

The following can be seen in the error log: "'user' entry ignored in -skip-name-resolve mode.". If set, causes lines with localhost to be ignored according to the log.
#Mysql create user network mask update
So: Case 0: Host = '10.10.10.10' (null test) update user set host='10.10.10.10' where user='foo' flush privileges Ĭase 1: Host = '%' update user set host='%' where user='foo' flush privileges Ĭase 2: Host = 'localhost' update user set host='localhost' where user='foo' flush privileges īehaviour varies and this apparently depends on skip-name-resolve. You will see something like: mysql quux 3u IPv4 0t0 TCP 127.0.0.1:->127.0.0.1:mysql (ESTABLISHED)

To connect to the server from "127.0.0.1" instead, run this on the command line mysql -pbar -ufoo -bind-address=127.0.0.1 -protocol=TCP One expects that the above matches "user comes from localhost" but certainly not "user comes from 127.0.0.1". the I/O pipe that is named by the filesystem entry /var/run/mysqld/mysqld.sock or some such), run this on the command line (use the -protocol option to make doubly sure) mysql -pbar -ufoo To connect to the Unix Domain Socket (i.e. | version | 10.0.23-MariaDB-0+deb8u1-log |Ĭreate a user foo with password bar for testing: CREATE USER IDENTIFIED BY 'bar' FLUSH PRIVILEGES Connect as superuser, and then: SHOW VARIABLES LIKE "%version%"
