View previous topic :: View next topic |
Author |
Message |
Lancelightt
Joined: 04 Jan 2006 Posts: 2
|
Posted: Wed Jan 04, 2006 10:28 Post subject: Changing the .sock location |
|
|
Is there any way to change where it looks for the mysql.sock file? I run a Mandrake based distro and it keeps the sock file in /var/lib/mysq/mysql.sock but the nwnx2 Lib seems to look for it at /var/run/mysqld/mysql.sock. Now, I can put a Symlink to it, but everytime I restart the mysql server, the symlink is deleted for some reason. The correct way to fix this would seem to be able to point nwnx2 to the right place. |
|
Back to top |
|
|
Parsec
Joined: 06 Jan 2005 Posts: 7
|
Posted: Thu Jan 05, 2006 14:31 Post subject: |
|
|
Hmm if it's like many other linux distro's there will be a mysql config file in /etc/mysql. If not look for the mysql config file.
The mysql config file allows an option for the location of the mysql.sock, so just change it and restart mysql.
eg:
socket = /var/run/mysqld/mysqld.sock
or mysql.sock whatever - make sure the directory exists and the permissions are ok on it. |
|
Back to top |
|
|
Lancelightt
Joined: 04 Jan 2006 Posts: 2
|
Posted: Tue Jan 10, 2006 5:11 Post subject: |
|
|
I would do that, except that other apps that I run look for it in /var/lib/mysql and symlinks for those apps do NOT work for some reason. I wish they also would allow you to set where to look for the sock file, but they dont either. This is one of the biggest problems with Linux/Mysql developers. They seem to think that leaving out an ini config option for .sock is ok. Its NOT ok. I dont know how else to explain that its something that should be looked at for the next version.
As I stated in my previous msg, the symlink seemed to work ok, but its not the correct way to go about doing things. I was simply stating that in the next version or maybe an update, that there should be an option to change it in nwnx2.ini. This will affect any nwnx2 setup that uses "localhost" on a linux machine. If you do not use localhost, then it will attempt to connect to port 3306 on whatever IP or Name you give it which is the correct behavior.
I hope to see an option for it in a future version, it would make life easier for me at least. |
|
Back to top |
|
|
|