SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm sure lots of you are probably experiencing this.. I googled around and found this, tried it out and it works perfect.. looks like the owner is incorrect on some of the files in /var/lib/mysql/mysql
They should be owned my the mysql user, not root.
just do this..
chown -R mysql /var/lib/mysql
then either chmod +x /etc/rc.d/rc.mysqld ( if its not already )
or, to test it.. run: /usr/bin/mysqld_safe &
also --- you might have to run mysql_install_db .. not sure if I had to do that first..
It's also explained in /etc/rc.d/rc.mysqld script which say:
# Before you can run MySQL, you must have a database. To install an initial
# database, do this as root:
# su - mysql
# Note that step one is becoming the mysql user. It's important to do this
# before making any changes to the database, or mysqld won't be able to write
# to it later (this can be fixed with 'chown -R mysql.mysql /var/lib/mysql').
Well, those instructions are a little late.. I think if the install gives you the option of starting it automatically when you boot up, this should be done for you during the install. If someone is bright enough to edit the rc.mysqld script and read the instructions, then I think they are bright enough to chmod +x the script. I don't think it should be a startup option on the install if it's not going to work automatically. That's just my opinion.
We're too late? You posted at " Today 05:58 AM" and we answered just two hours later
[Moderator Edit: Please refrain from using abusive language].
What I meant by those instructions being late is.. after you tell Slackware ( in the install ) to start mysqld on boot up, but no tables have been created and it fails to start on bootup.. THAT is too late. Not his or your instructions..
The reason I said reboot is so that people can see that it will startup correctly from the init scripts at bootup. I *also* noted the option of just running /usr/bin/mysqld_safe & to show that it works that way as well. I personally, after adding new services to my system like to reboot and make sure everything starts like it should.