![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
End runs don't generally work, but...
Jul. 31st, 2000 09:30 amSo I went to sleep last night while MySQL was compiling (and on a 486, that takes some time!). Got up this morning, and everything seemed to be okay. Killed the existing mysqld processes and did a make install, then ran safe_mysqld to restart.
No joy. Running `mysqladmin variables' tells me that the socket file is in `/var/lib/mysql/mysql.sock', just as before. The problem is that when PHP goes looking to connect to a MySQL database from the web script, it seeks the socket file in `/tmp/mysql.sock'.
Apparently, my attempt to configure MySQL to use the `/tmp' path for the socket file didn't work, or I didn't write the instruction correctly, or something.
The whole point of this exercise, by the way, is to try out a PHP-based messaging system called `VenomBoard', which appears to work fairly well on the web site of the fellow who wrote it. I downloaded the source and had to play around some with it - the code is straighforward - but I've not been able to get it to work on `kerouac' because I've been unable to connect to the forum database using mysql_connect().
When all of a sudden, I start to think, why not create `mysql.sock' in the `/tmp' directory as a symbolic link to the real socket file? So, I enter the following:
[alex /tmp]# ln -s /var/lib/mysql/mysql.sock mysql.sock
which works (why shouldn't it?). Then I try the long-suffering script via the web. It appears to work. It's slow, but what do you expect from a 486?
So the $64,000 question is: How good/bad an idea was this? Sure, it works, but is there some `gotcha' waiting in the wings for me to turn my back?
There's some additional work left to do before porting the deal to a production-quality server. But in principle, doing all of this happy stuff on a 486 has helped sharpen my programming and administration skills.
Two days and a wakeup left until I go back to work. Let's not lose time! Later.
Cheers...
No joy. Running `mysqladmin variables' tells me that the socket file is in `/var/lib/mysql/mysql.sock', just as before. The problem is that when PHP goes looking to connect to a MySQL database from the web script, it seeks the socket file in `/tmp/mysql.sock'.
Apparently, my attempt to configure MySQL to use the `/tmp' path for the socket file didn't work, or I didn't write the instruction correctly, or something.
The whole point of this exercise, by the way, is to try out a PHP-based messaging system called `VenomBoard', which appears to work fairly well on the web site of the fellow who wrote it. I downloaded the source and had to play around some with it - the code is straighforward - but I've not been able to get it to work on `kerouac' because I've been unable to connect to the forum database using mysql_connect().
When all of a sudden, I start to think, why not create `mysql.sock' in the `/tmp' directory as a symbolic link to the real socket file? So, I enter the following:
[alex /tmp]# ln -s /var/lib/mysql/mysql.sock mysql.sock
which works (why shouldn't it?). Then I try the long-suffering script via the web. It appears to work. It's slow, but what do you expect from a 486?
So the $64,000 question is: How good/bad an idea was this? Sure, it works, but is there some `gotcha' waiting in the wings for me to turn my back?
There's some additional work left to do before porting the deal to a production-quality server. But in principle, doing all of this happy stuff on a 486 has helped sharpen my programming and administration skills.
Two days and a wakeup left until I go back to work. Let's not lose time! Later.
Cheers...
