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.
Is it running? Try "ps -e | grep mysql" to see if processes are running.
Make sure /etc/rc.d/rc.mysqld is executable.
You can start it using:
/etc/rc.d/rc.mysqld start
i don't see a rc.mysqld file in the /etc/rc.d directory..... i know i messed up somewhere, but is the file automatically generated or do i have to make up a script ?
ok, i finally managed to copy the executable script from mysql/support-files to /etc/rc.d , and i have the daemon running, but when i try to do /usr/local/bin/mysql, it comes up as :
ERROR 1045: Access denied for user : 'root@localhost' (Using password: NO)
i know this has something to do with the mysql user, but i'm stuck in a rut with this one.
thanks for all your help
"ERROR 2002: Can't connect to local MySQL server through socket '/var/run/mysql.sock' (2)
I did the mysql_install_db thing like it said at http://www.unixfool.com/mysql-slack.shtml, it does it without any errors, but then when I type mysql again, it shows the same old error. I had this problem when I installed Slack 9.1, official packages. Now I'm having the exact same problem after doing a clean install of slack 10.
Hey TBomb do you have a firewall running? MySQL needs port 3306 to work trough socket.
brokenflea, that means that you have to supply a password when trying to connect, if i don't remember wrong you have to issue the mysql command with the -p parameter.
Check your mysql config file and see if you have this:
Code:
# The following options will be passed to all MySQL clients
[client]
port = 3306
socket = /var/run/mysql/mysql.sock
# The MySQL server
[mysqld]
port = 3306
socket = /var/run/mysql/mysql.sock
And this line must not exist or be commented like here (i'm talking about skip-networking line):
Code:
# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (using the "enable-named-pipe" option) will render mysqld useless!
#
#skip-networking
By the way, it's strange that you have /var/run empty, a lot of programs (like Apache, Samba, SSH) uses it as a holding directory for their pids or socks.
damnit, I can't even start up KDE now. My computer was booting into gnome rather than KDE, so I changed /etc/rc.d/rc.4 and removed the gnome entry, so that it would load kde by default.
Just rebooted and it's still going to the gnome login manager, I tried logging in again to change the file again, but it just freezes when the gnome logo appears.
All fixed When I changed the permissions of the directory, I assumed it would automaticly change the permissions of all files and folders under it, it didn't. Changed them all manually and it works!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.