HI All,,, Since last night when I sent this email I reinstalled mysql. This did not help. But I noticed that the mysqld was dieing as soon as I booted the system. How can I tell what is wrong with the daemon? TIA JIM On Sunday 23 February 2003 20:43, you wrote:
Thanks Tom,
But that did not work :( BTW I've rebooted a couple of times since I messed up.
Any other ideas?
TIA
JIM
On Sunday 23 February 2003 20:09, Tom Emerson wrote:
On Sunday 23 February 2003 6:43 am, James Hatridge wrote:
Ok, I really stepped on it today. I deleted "mysql.sock". After a few minutes of good southern cussn' I copyed it from another system. [...]
As you've no doubt found out by now, "socket" files aren't normal files.
The data they contain is fleeting at best -- the idea is that "some process" is continually reading the file looking for commands or data [your mysql daemon in this case] and once read, the data is removed from the file.
When mysql starts up, it is responsible for the creation and management of these "unix socket" or "pipe" files, so I *think* all you need to do after "accidentally" purging the mysql.sock file is simply restart the mysql server. [as root, type "rcmysql restart", but note "mysql" might have a trailing "d" on it, as in "mysqld"]
-- Jim Hatridge Linux User #88484 ------------------------------------------------------ BayerWulf Linux System # 129656 The Recycled Beowulf Project Looking for throw-away or obsolete computers and parts to recycle into a Linux super computer