In the last years we have tested and ran multiple PHP op-code caching software for forums, php powered web sites and WordPress blogs. Performance wise the eAccelerator was our top-performer and we haven’t experienced problems with it.

eAccelerator is also a good choice for WordPress blog hosting and this op-code cache doesn’t cause problems with WP plugins – WP Super Cache, WP Cache and even when you run memcached caching.

Our standard settings for eAccelerator in 99% solutions is as follows:

zend_extension=”/usr/local/lib/php/extensions/no-debug-non-zts-20060613/eaccelerator.so”
eaccelerator.shm_size=”16″
eaccelerator.cache_dir=”/tmp/eaccelerator”
eaccelerator.enable=”1″
eaccelerator.optimizer=”1″
eaccelerator.check_mtime=”1″
eaccelerator.debug=”0″
eaccelerator.filter=””
eaccelerator.shm_max=”0″
eaccelerator.shm_ttl=”0″
eaccelerator.shm_prune_period=”0″
eaccelerator.shm_only=”0″
eaccelerator.compress=”1″
eaccelerator.compress_level=”9″

We have been experiencing updating problems on SLES 10 SP 2 box and here is the error we got:

ERROR: Failed to download XML metadata: Download failed: (https://nu.novell.com/repo/repoindex.xml) Invalid certificate received form server.

To fix the problem do the following.

Open /etc/zmd/zmd.conf file that will look something like this:

[Advanced]
run-transaction-test=False
security-level=signature

[Server]
bind-ip=127.0.0.1
software-inventory-enabled=False
refresh-interval=86400
remote-enabled=false
require-verified-certs=True
hardware-inventory-enabled=False

[Network]
proxy-url=
proxy-password=
proxy-username=

[Cache]
cache-max-size-in-mb=300

[Debug]
log-soap-xml=False
log-exception-traces=False

and replace

require-verified-certs=True

with

require-verified-certs=False

For one project we are currently implementing ethernet channel bonding on Suse SLES 10 SP 2. It works like a wonder and Yast2 doesn’t interfere or re-configure the ethernet card configuration. More information with detailed how-to paper will follow.