If your computer has upgraded to IE7, and people are reporting design issues in IE6 or lower, you can download and run standalone version of older IE’s to test and fix the design. There is no installation to do, only run the program.
If your temporary files are growing too many too quick (say the working file of mod_gzip, sessions), there is an easy solution to clean up. Run:
root# tmpwatch 1 /dev/shm/mod_gzip
This cleans up the file that have not been accessed for one hour. See man tmpwatch for more information
This is old material as you should be using eAccelerator now. Install from source or best yet, RPM). This is for reference or for those who have not made the switch.
Step 1. Compiling Turck MMCache
You must specify the real prefix where PHP is installed in the “export” command. It may
be “/usr” “/usr/local”, or something else.
Step 2. Installing Turck MMCache
Step 3. Configuring Turck MMCache.
Turck MMCache can be installed both as Zend or PHP extension, so you need to edit your
php.ini file (usually /etc/php.ini). To install as Zend extension:
Step 4. Creating cache directory
The hash table size defines the number of top-level nodes for each child’s hash table. Increasing this number will provide faster performance by decreasing the number of iterations required to get to the record, but consume more memory for table space. You should increase this if you have a busy web server. The value you specify will automatically be tiered up to the next prime number in the primes list (see mod_evasive.c for a list of primes used).
This is the threshhold for the number of requests for the same page (or URI) per page interval. Once the threshhold for that interval has been exceeded, the IP address of the client will be added to the blocking list.
This is the threshhold for the total number of requests for any object by the same client on the same listener per site interval. Once the threshhold for that interval has been exceeded, the IP address of the client will be added to the blocking list.
The interval for the page count threshold; defaults to 1 second intervals.
The interval for the site count threshold; defaults to 1 second intervals.
The blocking period is the amount of time (in seconds) that a client will be blocked for if they are added to the blocking list. During this time, all subsequent requests from the client will result in a 403 (Forbidden) and the timer being reset (e.g. another 10 seconds). Since the timer is reset for every subsequent request, it is not necessary to have a long blocking period; in the event of a DoS attack, this timer will keep getting reset.
If this value is set, an email will be sent to the address specified whenever an IP address becomes blacklisted. A locking mechanism using /tmp prevents continuous emails from being sent.