- Documentation Library
- Table of Contents
- MySQL 5.5 Manual
- MySQL 5.4 Manual
- MySQL 5.1 Manual
- MySQL 5.0 Manual
- MySQL 3.23/4.0/4.1 Manual
- Table of Contents
- 2 Installing and Upgrading MySQL
- 2.1 General Installation Issues
- 2.2 Standard MySQL Installation Using a Binary Distribution
- 2.3 Installing MySQL on Windows
- 2.4 Installing MySQL from RPM Packages on Linux
- 2.5 Installing MySQL on Mac OS X
- 2.6 Installing MySQL on Solaris
- 2.7 Installing MySQL on NetWare
- 2.8 Installing MySQL from tar.gz Packages on Other Unix-Like Systems
- 2.9 MySQL Installation Using a Source Distribution
- 2.10 Post-Installation Setup and Testing
- 2.11 Upgrading or Downgrading MySQL
- 2.12 Operating System-Specific Notes
- 2.13 Environment Variables
- 2.14 Perl Installation Notes
[+/-]
After installing MySQL, there are some issues that you should address. For example, on Unix, you should initialize the data directory and create the MySQL grant tables. On all platforms, an important security concern is that the initial accounts in the grant tables have no passwords. You should assign passwords to prevent unauthorized access to the MySQL server. Optionally, for MySQL 4.1.3 and up, you can create time zone tables to enable recognition of named time zones.
The following sections include post-installation procedures that are specific to Windows systems and to Unix systems. Another section, Section 2.10.2.3, “Starting and Troubleshooting the MySQL Server”, applies to all platforms; it describes what to do if you have trouble getting the server to start. Section 2.10.3, “Securing the Initial MySQL Accounts”, also applies to all platforms. You should follow its instructions to make sure that you have properly protected your MySQL accounts by assigning passwords to them.
When you are ready to create additional user accounts, you can find information on the MySQL access control system and account management in Section 5.5, “The MySQL Access Privilege System”, and Section 5.6, “MySQL User Account Management”.
User Comments
Re the alter-table 'prompt' when invoking run-all-tests:
It looks like a prompt. Keep waiting.
On my Solaris 2.8 system running MySQL 3.23.46, that first test suite took 18 minutes to complete (on a Sun Blade 100 with 500MHz, 640 MB, files NFS mounted).
The unix 'truss' command showed that the test script was active. If you log into the MySQL server, you will see that there is activity (use test; show tables; describe bench;).
If you are running RedHat Linux (not sure which versions) you may run into a problem with the mysql-test/mysql-test-run script unless you have your locale configured to POSIX. The other locales seem to sort "repair_part2" before "repair" and that causes repair_part2 to fail. Be sure to set your LANG environment variable to C or POSIX before running the tests.
With Fedora Core 1 (and probably RH9), it isn't necessary to run mysql_install_db yourself. To start mysqld, use "/etc/rc.d/init.d/mysqld start". The first time this is run, the database is initialized (with mysql_install_db), and the ownership of /var/lib/mysql/ is set to mysql:mysql.
You need to run chkconfig or redhat-config-services to have mysqld started on bootup.
Slackware users make sure you create the link:
ln -s /var/run/mysql/mysql.sock /tmp/mysql.sock
The client libraries may fail to run, otherwise.
Regards,
-Kenan Bektas
I'm a Slackware linux user and I had exactly the same problem.
In my case the reason was that I had an old /etc/my.cnf file, I copied one of the configuration files (my-medium fits well for me) provided in mysql/support-files to /etc/my.cnf and after restart of mysql server everything works fine. (The socket for server and clients is specified in my.cnf file)
After many hours of seeing "cannot find mysqld.pid" I commented out the reference to mysqld.pid in the mysqld_safe section of /etc/my.cnf and the system finally came up.
Add your own comment.