I could not start ./safte_mysql.
Error message: touch: /usr/local/mysql/var/gemini.err cannot create chown: /usr/local/mysql/var/gemini.err: No such file or directory Starting mysqld daemon with databases from /usr/local/mysql/var ./safe_mysqld: /usr/local/mysql/var/gemini.err: cannot create
the "var" directory used to be called "data" and at least is still data in the binary distribution of mysql
So I created the directory of var, and restarted ./safe_mysqld
your gemini.err says mysqld cant write to the /usr/local/mysql/var directory you just created.
Did you change the owner of this directory to the user "mysql" ?
Thats the user id that mysqld runs under and therefor it needs write permission for it's data-directory.
The docu says somewhere that you can't start ./safe_mysqld when you are in the bin-directory.
You have to cd /usr/local/mysql and execute ./bin/save_mysqld
You can't directly run /usr/local/mysql/bin/save_mysqld either.
AND you can't successfully run ./bin/save_mysqld & when you are running it within mc. You can without the '&' but then the shell with mc is blocked.
If you run a distribution like SuSE which puts none of it's own stuff in /usr/local at all but in /usr so /usr/bin is cluttered with all kinds of applications, then you'll run into further hassle by putting the mysql.com binary into /usr/local/mysql.
mysql.com's binaries put the socket into /tmp but SuSE has data and the lot of other stuff including the socket in /var/lib/mysql.
So the SuSE provided client applications won't find the socket and you get a running mysqld which you cant't connect to on your own host.
make a symlink from /tmp/mysql.sock to /var/lib/mysql.sock
It's a funny world ...
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
