Menu
MySQL 4 is one of the most successful versions of the best free database. The simplicity of this database made many web developers implement it on their sites, developments and to provide their knowledge, which transformed MySQL 4 into the center of almost all web developments. Among it features you will find the possibility to perform secure connections, replication or search and index text fields. It also had a lot of repercussion due to the fact that it was multi-platform and that it had a large SQL language pack. Since it's open source, many companies adapted it to their own needs and very little time went by before it was accepted by the majority of people in what regards to databases focused on websites.
Its InnoDB storage engine and the speed with which it works managed to make MySQL 4 withstand for more than 6 years in a world that is ever changing like the Internet, being launched in 2002, and not being completely substituted until 2009. If you use content managers like Joomla, Wordpress or PHP-Nuke, you'll probably need a database like MySQL 4 for them to work.
Hello, I'm trying to compile MySQL 4.1.22 from soucre on CentOS 4. So you'll know what I'm using, this is my /proc/version: Linux version 2.6.18-8.el5 (gcc version 4.1.1 20070105 (Red Hat 4.1.1-52)) #1 SMP Thu Mar 15 19:46:53 EDT 2007 I've tried many different configuration settings when building MySQL and always run into the same problem, so I've defaulted to using no config settings for the purpose of reporting here. I've already created a mysql group and mysql user. I'm just unpacking the source into it's own directory and then doing a:./configure make make install After installing, I run /usr/local/bin/mysqlinstalldb and that runs without any errors and creates all of the default databases. Then I set permissions on the database files: chown -R mysql:mysql /usr/local/var Then I try to start the server: /usr/local/bin/mysqldsafe -user=mysql & At this point, I get: 'Starting mysqld daemon with databases from /usr/local/var' And then it seems that mysqld hangs. I am not returned to a command prompt and I do not receive the message that it is waiting for connections. It just sits and never returns to the command prompt unless I break out.
If I break out and run 'top', I can see that mysqld is running. At that point, if I try to use mysql to log into the server, mysql crashes with a segmentation fault. Mysqld will continue to run until I reboot the server. It will show up in ps ax grep mysqld or in 'top', but I can't access the server from the mysql client program due to the segmentation fault. I'm assuming that the server really isn't running properly and that this is why mysql is crashing.
I've built with debug and found something interesting in the trace file. Even though when I start the server using the -debug option, it never says that it's waiting for connections (and still hangs), I find at the very end of the trace file, a message that the server is waiting for connections. I'm totally stumped here. Rondo veneziano best of rar. I also tried building with the latest 5.2 version of MySQL and ran into the exact same problem. I've tried checking for obvious things (made sure there was no my.cnf file on the system). I have a feeling though that I'm overlooking something really simple and newbish, as I've never built MySQL from source before (I do routinely compile many other programs from source without any trouble).
Thanks in advance for any ideas. Update: I tried running a binary installation: mysql-standard-4.1.22-pc-linux-gnu-i686-icc-glibc23.tar.gz I followed the steps for setting up the binaries, creating the database, giving ownership to mysql, etc. Everything seemed to go just fine until I tried to start the server and the same thing happened. root@localhost mysql# bin/mysqldsafe -user=mysql & 5 3417 root@localhost mysql# Starting mysqld daemon with databases from /mnt/drive2/mysql/data After the above line is displayed, it seems to hang. As before, the command prompt never returns.
(This time I set up the database files in a different location, I don't think that would make a difference.) I'm thinking this rules out anything I might be doing when I build it and points to something that happens at run time. Am I just not starting up the server properly? Am I missing something simple here? Thanks again. I was not able to compile PHP using the libraries from the RPM installation of MySQL. I run into very strange problems while configuring PHP when doing so. I installed the following MySQL RPMs: MySQL-client-standard-4.1.22-0.rhel4.i386.rpm MySQL-devel-standard-4.1.22-0.rhel4.i386.rpm MySQL-server-standard-4.1.22-0.rhel4.i386.rpm They installed just fine and the server was up and running.
However, when I ran my./configure script in PHP, I got the following errors: checking for mysqlclose in -lmysqlclient. No checking for mysqlerror in -lmysqlclient. No configure: error: mysql configure failed. Please check config.log for more information. From config.log: /usr/bin/ld: skipping incompatible /usr/lib/mysql/libmysqlclient.a when searching for -lmysqlclient /usr/bin/ld: cannot find -lmysqlclient So it appears that for some reason the libmysqlclient.a file installed by the MySQL RPM is not compatible? I was hoping to get the correct library files for PHP by installing from source. I should note, I got these RPM files from the MySQL website.
Mysql 4.1.22 Allow Root From Ip
Does CentOS provide any MySQL 4.1.x RPM files? Yum doesn't seem to be an option for me because I can't find any MySQL 4.1.x yum packages (they're all 5.x). Also, I do need to compile PHP from source as there are simply way too many extras and patches that I need to apply. So doing an RPM install of MySQL would be fine if I could build my PHP installation using it's libraries.
Users are created the first time you GRANT them a privilege. From: The GRANT statement creates MySQL user accounts and grants rights to accounts. So, let's say you have a database 'mydb', with a table 'mytable'. If you want to create a user 'jason', with the password 'pwd123!'
Mysql 4.1.22 Windows
Who has SELECT privileges on this table, you can do this: grant select on mydb.mytable to 'jason'@'hostname' identified by 'pwd123!' ; The usual caveats about hostname apply. If you want to give jason full permissions on mydb: grant all on mydb.
to 'jason'@'hostname' identified by 'pwd123!' ; Important note: every time you use identified by, you're changing the password for that user/hostname, so you you will typically only use this syntax when creating a user!
The simplicity shown by MySQL 4 managed to place it among the most used databases, something that, together with the license that allowed it to be distributed without any problems, managed to convince many developers to devote themselves to its development and made it one of the most important databases. Despite the fact that its first versions didn't have some key functions like transactions or the reference integrity, the truth is that with regard to its performance and usability, MySQL 4 is an excellent database to use on web servers that support dynamic websites. Among its most important features, we will be able to us the organization by means of foreign keys, replication or the possibility to index text fields. What's more, its optimization can be based on improving its speed or the amount of simultaneous operations available. MySQL 4 is a really popular development, over which the vast majority of CMS that have appeared on the current market can be used, like Wordpress, Joomla or Drupal. So now you know, if you want to learn how to use and optimize the functioning of databases focused on the web, this software is the first thing that you have to download.
I'm working with someone who is having MySQL connection problems, and is running MySQL 4.1.22. The root password seems to have been lost or changed, and I'm having a hard time getting it correctly changed. Here's what I've tried:. Added skip-grant-tables to their my.cnf. Restarted MySQL. Successfully logged into MySQL. Run the following: mysql use mysql; Database changed mysql update user set password=PASSWORD('thepassword') where User='root'; Query OK, 2 rows affected (0.03 sec) Rows matched: 2 Changed: 2 Warnings: 0 mysql flush privileges; Query OK, 0 rows affected (0.00 sec).
Remove skip-grant-tables from my.cnf and restart MySQL. However, this doesn't seem to resolve the issue, and still prevents access to MySQL as root with the correct password. Anyone have any ideas? I'm not too savvy with MySQL 4, so I may be doing something wrong here, but from what I've read that should work.