Upgraded to 4.0.16 from 3.2.x --- why did service file change?
I upgraded from RPM and I noticed that the /etc/rc.d/init.d script was changed from mysqld to mysql. It also appears as if the 'status' option that you can pass into service was removed. I'm just curious why the owners would do that? What is the rationale to changing a script name and removing funtionality? It just seems to break all scripts that relied on that functionality -- am I missing something? Thanx, brian -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Upgraded to 4.0.16 from 3.2.x --- why did service file change?
On Tue, 2003-11-11 at 16:04, Dathan Vance Pattishall wrote: - Dathan Vance Pattishall - Sr. Programmer and mySQL DBA for FriendFinder Inc. - http://friendfinder.com/go/p40688 ---Original Message- --From: Brian Snyder [mailto:[EMAIL PROTECTED] --Sent: Tuesday, November 11, 2003 12:51 PM --To: [EMAIL PROTECTED] --Subject: Upgraded to 4.0.16 from 3.2.x --- why did service file change? -- --I upgraded from RPM and I noticed that the /etc/rc.d/init.d script was --changed from mysqld to mysql. It also appears as if the 'status' option --that you can pass into service was removed. -- --I'm just curious why the owners would do that? Maybe because your actually not starting the mysqld daemon, your starting a wrapper script. --What is the rationale to changing a script name and removing --funtionality? No functionality has been removed. What are you noticing? The old mysql service script was called mysqld , the new one is called mysql. You used to be able to say 'service mysqld status' and get an OK if running. Now support for status was removed, and its just start, stop, and restart. BTW, This is on redhat. brian -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Upgrading help please
Andrew, I had the same problem and had to stop and restart the servers. Give that a shot. brian On Wed, 2003-11-05 at 17:19, Andrew wrote: Good day List, I have just upgraded from 3.23 -4.0.16 I downloaded all the RPM's and then ran rpm -U *.rpm It did all that it was supposed to do, and then told me to use the /usr/bin/mysql_fix_privilege_tables script which I did got horrid errors ERROR 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) So I specified mysql_fix_privilege_tables root_password Same Errors (2002) Tried the other method that is on the mysql manual mysql_fix_privilege_tables --password=root_password Same error 2002. now Unfortunately I am unable to even connect to mysql with either mysqladmin or the client. MySQL-bench-4.0.16-0.i386.rpm MySQL-client-4.0.16-0.i386.rpm MySQL-devel-4.0.16-0.i386.rpm MySQL-embedded-4.0.16-0.i386.rpm MySQL-Max-4.0.16-0.i386.rpm MySQL-server-4.0.16-0.i386.rpm MySQL-shared-4.0.16-0.i386.rpm MySQL-shared-compat-4.0.16-0.i386.rpm is a list of the RPMS that I downloaded and ran. Any ideas and help would be most appreciated. Thank you Andrew Message sent using UebiMiau 2.7.2 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Question about compability of clients and the deamon
Hi all, I am investigating upgrading from our current release of MySql. (We use Red-Hat 7.2 and it ships with 3.23.41). Anyway, I am interested in upgrading to either the latest 3.23 release or the latest stable 4.0 release. My concerns are which is an easier and/or less risky upgrade? We have our own server programs that use mysql embedded libraries to access the database.. since the development rpms have been updated, I assume changes have been made to this stuff -- but is it as easy as just recomplining? Does code typically have to be altered (for either release)? And last but not least, if we install mysql4 on a machine but then want to downgrade server revisions, would they be compatible to each other? IE: If we compile a server against the 4.0 development rpms, could it run against a 3.2 deamon... and vice versa? I've been reading alot about upgrading on the website and it seems to point towards an easy process, but my boss is very nervous about it - and I was hoping to get some 'been-there-done-that' advice from the group. Cheers, --brian -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
