Quote:
Originally Posted by kmike
There is no need for calling eaccelerator_rm() there, eaccelerator_set() takes care of replacing the older value with a new one. That being sad, it's extremely strange that PHP timed out on that call, it simply shouldn't happen.
The only possible cause I could think of is that maybe eAccelerator is set to cache everything on disk, and the disk I/O was blocked for some reason, and thus eAccelerator couldn't remove the old value.
|
It seemed like a best practice at the time really, and with the API on eAccelerator being fairly vague and the function appearing to do no harm (until this odd situation) I figured better to be safe than sorry. If it keeps happening for the user they can comment the line out, but honestly that may just be ignoring the problem as it seems to be a lot deeper.