Atomicorp

So do I keep one of them? Or get rid of both like this: [main] cachedir=/var/cache/yum debuglevel=2 logfile=/var/log/yum.log pkgpolicy=newest distroverpkg=redhat-release tolerant=1 exactarch=1 retries=20 [base] gpgcheck=1 name=Fedora Core $releasever base baseurl=http://download.fedoralegacy.org/fed...

Don't need these: [base] name=Atomic Rocket Turtle - $releasever - Base OS RPMS mirror baseurl=http://3es.atomicrocketturtle.com/3rd-party/base/$releasever/ [updates] name=Atomic Rocket Turtle - $releasever - OS Update RPMS mirror baseurl=http://3es.atomicrocketturtle.com/3rd-party/updates/$releasev...

Would this be the proper setup for fedora legacy? [main] cachedir=/var/cache/yum debuglevel=2 logfile=/var/log/yum.log pkgpolicy=newest distroverpkg=redhat-release tolerant=1 exactarch=1 retries=20 [base] gpgcheck=1 name=Fedora Core $releasever base baseurl=http://download.fedoralegacy.org/fedora/$r...

I'm really interested in know what other FC2 user's yum.conf files look like. Here's what mine looks like. I added the ART channels and the rest was already installed by my host, iweb.ca: [main] cachedir=/var/cache/yum debuglevel=2 logfile=/var/log/yum.log pkgpolicy=newest distroverpkg=redhat-releas...

I'm thinking of first applying these changes: Upgrading from ART PHP 4.4.2 Remove incompatible packages: yum remove php-mcrypt php-xslt php-domxml Update PHP: yum upgrade Install additional packages: yum install php-gd Correct Configuration files (if needed): mv /etc/php.ini /etc/php.ini.v4 mv /etc/...

I ran yum check-update and got this back: php i386 5.0.4-13.rhfc2.art atomic php-imap i386 5.0.4-13.rhfc2.art atomic php-mbstring i386 5.0.4-13.rhfc2.art atomic php-mysql i386 5.0.4-13.rhfc2.art atomic php-pear i386 5.0.4-13.rhfc2.art atomic php-pgsql i386 5.0.4-13.rhfc2.art atomic spamassassin i386...

I'm currently only using yum to update my server. Is this good enough? I had a problem in the past with the built in Plesk updater, which is why I switched to ART.

The zend issue wasn't serious, it just took me forever to figure out. Your right I should get another server for testing.

What's the best way to update zend?

My last yum update didn't go so smoothly because of my zend optimizer. Do these latest updates look ok? Any problems anyone can think of? # yum check-update Repository base already added, not adding again Setting up Repos psa-7.5 100% |=========================| 951 B 00:00 base 100% |==============...

Is the ImageMagick installation fairly stable? I know it's included in the ART rpms somewhere.

OK, I think I have it figured out now. I commented out the the fields in both

ioncube-loader.ini
and
ioncube.ini

The zend seems to work fine now. I just got it working through trial and error. Why was this causing the problem?

This seems to be the consistent error: PHP Fatal error: [ionCube Loader] The Loader must appear in the php.ini file before other extensions in Unknown on line 0 Failed loading /usr/lib/php4/ioncube_loader_lin_4.4.so: /usr/lib/php4/ioncube_loader_lin_4.4.so: cannot open shared object file: No such fi...

The ioncube.ini file contains this link:

I commented out the zend optimizer from php.ini, and everything loads (except for the sites that need zend of course).

So it's definitely zend that's causing the problem. I'm just not sure how to fix it.

My php.ini currently has this: [Zend] zend_extension_manager.optimizer=/usr/local/Zend/lib/Optimizer-2_6_2 zend_extension_manager.optimizer_ts=/usr/local/Zend/lib/Optimizer_TS-2_6_2 zend_optimizer.version=2.6.2 zend_extension=/usr/local/Zend/lib/ZendExtensionManager.so zend_extension_ts=/usr/local/Z...