Am 25.05.2011 22:15, schrieb Jesse Norell: > On Sat, 2011-05-21 at 12:19 +0200, Reindl Harald wrote: >> >> yes the socket should be preferred i think because it is faster >> or normally "localhost" means socket in every case for mysql >> (mysql-cli, php) and if you want to use TCP you have to configure >> "127.0.0.1" (or a socket) >> ____________________________ >> >> mysql --socket=/var/lib/mysql/mysqld_dbmail.sock -u root -p >> using the socket and the second mysqld-instance >> >> mysql --socket=/var/lib/mysql/mysqld_dbmail.sock -h localhost -u root >> -p >> does the same and -h localhost is nice but useless >> >> mysql --socket=/var/lib/mysql/mysqld_dbmail.sock -h 127.0.0.1 -u root >> -p >> ignores the socket because 127.0.0.1 switches to TCP >> ____________________________ >> >> dbmail himself perefers the second version or is falling back to the >> default mysqld (default-socket or TCP is not clear for me) if >> "sqlsocket" has a non-default-value and "host = localhost" is missing >> >> in my optinion this is a small bug in dbmail and both should act >> like the official client-software or if there is a good reason >> for a difference you and paul could make clear what way to go >> so that a config-file can be used for both in all setups > > > Try commit ca037066476877c3617c for this
thank you! works now with socket-configuration independent of "host = localhost" or not great piece of work for such a new daemon!
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
