Quote:
Without the extension installed it is impossible for any php script to use eAccelerator functions
|
That's so incorrect it's not even funny. Eaccelerator works FINE without the above compiled option. If it didn't, it would be put in the recommended settings.
I've had eaccelerator running for years. Cache? Right now, it's running at 30.30% (155.12MB/ 512.00MB), with the top script (right now) being accessed over 4k times since the last time it was cleared. There is no way you can NOT tell me eacc does not work properly, because it does.
Quote:
Incorrectly setting up eAccelerator is your fault - don't blame this script for a crippled eAccelerator installation.
|
Again,
wrong answer. If you don't know what you're talking about, please, don't try to step in and say you do. From their INSTALLATION GUIDE!
Quote:
Step 1. Compiling eAccelerator
export PHP_PREFIX="/usr"
$PHP_PREFIX/bin/phpize
./configure \
--enable-eaccelerator=shared \
--with-php-config=$PHP_PREFIX/bin/php-config
make
You must specify the real prefix where PHP is installed in the "export"
command. It may be "/usr" "/usr/local", or something else.
|
Eaccelerator was
not installed incorrectly at all. This product requires advanced setups and should be modified to work with the EA recommended settings. I've been installing EA the exact same way (eventually you just script it

) for clients for years, numerous clients, over a good 30+ servers. Have ANY of them complained about it 'not working'? Nope.
Again, using the above settings, EA has worked, and has cached scripts for years. Right now, I'm at about 5GB cache (should probably clean some of that up

), but it most definitely DOES work properly, using the recommended , out of the box, settings.
This is not a problem with anything but products trying to force users into an advanced EA compile.