Search results

The default cache policy is conservative, do not cache request/response with cookies, do not cache request/response when cache-control does not allow caching. So, try a simple page like phpinfo() page first, on client side, check the request/response header with firebug to make sure there is no...

eaccelerator.shm_size="16" eaccelerator.cache_dir="/dev/shm/eaccelerator" eaccelerator.optimizer="0" eaccelerator.shm_only="0" create /dev/shm/eaccelerator/ directory with mode 777, this is for PHP suEXEC .

The "Customer Error Pages" are configured through Apache httpd.conf when use LiteSpeed with hosting control panel, the directive is "ErrorDocument". Most likely it has been configured by default, just need to add corresponding files under the document root.

You can copy your current php.ini to /usr/local/lsws/lsphp5/lib. Or, you can rebuild PHP5 by setting "Install Path Prefix" to "/usr/local", assuming apache php uses php.ini under /usr/local/lib/ directory.

increase "Memory soft/hard limit" as suggested.

If you use cPanel, just add a file "404.shtml" under "public_html" directory.

How long does it take to complete? There are various timeout parameters you need to adjust "Initial request timeout" for lsphp5 http://www.litespeedtech.com/docs/webserver/config/extapps/#initTimeout If it takes more than 5 minutes to process, you may need to add environment variable...

The best benchmark is your own result, it is pretty easy build Apache 2.2 with worker and comparing it to LiteSpeed in a real world setup. We will do benchmark tests after our 4.1 release.

That indicate a configuration problem, check /usr/local/apache/logs/error_log. fix the configuration.

Just use the rewrite rule you would use for Apache. extract subdomain from %{HTTP_HOST} with rewrite condition, then use %1, back reference to subdoamin as part of the destination url.

Yes, it should be fine. You probably wont need varnish with our mod_cache in 4.x release.

It is better to create a wiki directory and put Rewrite rule or redirect directive in .htaccess under that directory. The performance is better as the web server do not need to test it against every request, only when a request hitting wiki directory.

For security reason, LiteSpeed wont start untrusted process as root. A quick solution is to create a "setUid" wrapper for the piped logger, so it could run as root.

It is a page cache on disk, like Apache's mod_disk_cache.

please download the 4.0.4 release package and give it try. It should not give 503 errors when LSWS need to start a Rails application on demand. Just change the version number in the download link to get it.

For DirectAdmin, just do service lsws stop service httpd start or service apache start to switch from LSWS to Apache, vice versa for Apache to LSWS. For cPanel just login to WHM to use the plugin.

Please search the forum on this topic.

Have you tried eAccelerator again later. Is the eAccelerator code optimizer enabled? I wonder if the optimizer causes the trouble. Also, have you tried to strace the PHP process using too much CPU? Seems eAccelerator is the only solution work well with PHP suEXEC, need to find out why it...

I am not exactly sure, as the problem seems related to amount of script being cached. Or, maybe the eAccelerator optimizer causes trouble for latest PHP? Not sure.

Just comment out xcache related configuration form php.ini Yes, eaccelerator should help.