SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Can you briefly outline the steps you have already done in getting mysql setup
The error you specified means that either the mysql daemon isn't running, or the client is expecting the socket file to be in a different location that where mysqld is putting it.
Normally mysql data files are stored somewhere under /var. I *think* its /var/lib/mysql - I always move it elsewhere where there is more space and where I can more easily back up the data
i havent tocuhed mysql at all... i did a full install of slack 10.2 so i just assumed it would be setup and running (since apache was) and all id have todo was config it
i tried googling for a setup for 10.2 but found nothin
Mysql is not fully configured in default Slackware installation. You must configure it yourself as phil.d.g told. As well, read this /etc/rc.d/rc.mysqld.
Last edited by Alien_Hominid; 01-08-2006 at 01:57 PM.
By chmodding the rc script to 755 you made it so that mysqld starts on boot up.
I think the problem may be because mysqld isn't listening on a tcp port, in phpmyadmin's config.inc.php change the connection type to socket and the socket location to /var/run/mysql/mysql.sock
---
FOR MYSQLD: Now you have got it running you may want to read the my-*.cnf in /etc files and write a my.cnf to optimise mysql a bit for your circumstances and set your own options, as well as reading /etc/rc.d/rc.mysqld
You may need to comment SKIP="--skip-networking" in /etc/rc.d/rc.mysqld if your program connects using a tcp port.
Also there are some sample configuration files in /etc, all of them end with .cnf. Copy the one you need as /etc/my.cnf
Its probably because mysql isn't listening on a tcp port, only through that socket file. Unless you have remote clients connecting to mysql then there is no need to change this
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.