Atomicorp

Plus if you use x86_64 and eaccelerator you may have had a problem afterwards based on some of the other threads going around right now.

Any chance of this happening soon?

Ahh I see there is practically a duplicate of this already, you can delete this thread

Hello, We have seen a couple other threads regarding this or a similar issue with php-eaccelerator and was wondering when this could get "fixed". When doing a yum update it attempts to install the i386 package of php when we are running x86_64 builds. To illustrate the issue we uninstalled...

I wouldnt either, but I guess my question is really more in the line of - is it ok to install and have pear on your system in the first place, especially along with those items that it seemingly installs with it which are out of date. Does even having it on the system pose a risk?

Right, but isnt having pear arround at all (and the default modules that it installs, which are out of date) a security risk? # pear list-upgrades WARNING: channel "pear.php.net" has updated its protocols, use "channel-update pear.php.net" to update pear.php.net Available Upgrade...

php-pear is a dependency that gets installed with apc ============================================================================================================================================================================================================================================== Package...

Is it worth having to install pear (and not being able to update easily since popen is disabled by asl by default) and having those outdated packages for only a 5% increase?
I'm not a huge fan of having to update things outside of yum when it comes to php stuff.

Hello, I was wondering which one gives better performance? I've heard that APC does, and both of these are available from atomic, although neither one really seems to have been updated much in the last year. I also am not sure of pear, isnt it a potential security risk to have it arround? What do yo...

Try removing some lines from your my.cnf file - and check in your mysql log file to see if its complaining about something.

First off, when updating to the new mysql it installs an old version as a dependancy Then when it installs, it writes an error and mysql will no longer start. [code]Stopping mysqld: [ OK ] mysqld is alive Stopping mysqld: [ OK ] mysqld is alive Stopping mysqld: [ OK ] Starting mysqld: [ OK ] id: can...

I noticed that when it is updating mysql to 5.5.16-2 it is also installing mysql 5.1.59-1 as a dependancy - is that intentional?

the mysql-governor package is seperate, but requires a patch to mysql which I think he has already shared with cPanel for their build. it would be nice to have it included in yours as well so that if we continue to use your mysql then we could possibly still use this governor.

Any chance you could get with Igor from CL and encorporate his changes for the mysql-governor?

can you just use yum or rpm to remove the ones you dont want?

like
rpm -e mysql-5.1.57-1.el5.art --nodeps

Or does that kill them all then?