Delete and clear eaccelerator cache and set

The eaccelerator itself has the automatic clearing function. the specific setting options are as follows: eaccelerator. shm_ttl & quot; 600 & quot; when the eAccelerator fails to obtain the shared memory size of the new script, it will delete all the last & quot; shm_ttl & quot; in the shared memory; script cache that cannot be accessed within seconds. The... eaccelerator itself has the automatic clearing function. the specific settings are as follows: eaccelerator. shm_ttl = "600"
When the eAccelerator fails to obtain the shared memory size of the new script, it will delete all script caches that cannot be accessed in the last "shm_ttl" seconds from the shared memory. The default value is "0". that is, no cached files are deleted from the shared files in the spring.

Eaccelerator. shm_prune_period = "600"
When the eAccelerator fails to get the shared memory size of the new script, it will try to delete the cache script earlier than "shm_prune_period" from the shared memory. The default value is "0". that is, no cached files are deleted from the shared files in the spring.



Therefore, if it is not set to 0, it will be automatically cleared. if it is set to 0, it will be manually cleared.
Manually clear the directory. you can directly cache sub-directories in the directory and restart the web service.


Or clear it in the eaccelerator panel.

This article is excerpted from the linux Forum http://www.wdlinux.cn/bbs ~