Search results

Thanks! Bob. Like Xing said, 404 handler is used, however, rewrite rules will be honored if configured. A few more points regarding the new configuration: 404 handler is faster than rewrite rule. .htaccess support should be turned of when possible. There is no need to create dispatch.lsapi...

Yes, that should work. Or use "lsws/bin/lswsctrl restart". :cool:

That's because when you upgrade an older version, the installer will not overwrite your httpd_config.xml, so the template list has not been updated. The template files are there. You need to add them to the list manually. :)

You can search for "remote logging" solution for apache, LSWS can do exactly the same. Seems using syslogd is the simpliest solution. For using piped Logger, you can write a Perl script to forward content received from STDIN to remote server via TCP socket. On remote server, a deamon process...

Answers to both of your questions are "No" Not sure we are going to implement some thing like that at this moment.

You can LSWS as stateless load balancer as what you did with Mongrel cluster. We will release a dedicate load balancer which is session-aware. You can also use any other load balance proxies like apache, pond, etc., as long as it fits what your need. :)

For LSWS + Ruby LSAPI, just restart LSWS, restart is graceful, no downtime at all. LSRR is implemented on top of LSAPI, it is for running plain CGI scripts written in Ruby. Yes, you can do that. In that case, I would recommend running LSWS + LSAPI on each every cluster node with a...

Ruby LSAPI is the best choice for RoR. It gives the best performance as well the easiest configuration, the wiki uses Ruby LSAPI. LSRR is for running CGI in a persistent interpreter, ruby interpreter need to do extra work to shield one CGI script from interfering with the others, better using...

That's great! Thanks for you update! :-)

Amr, I think to build your own lsphp binary is more likely fix the problem. The MySQL client in the pre-built lsphp binary does not compatible with the new authentication method used by MySQL 4.1 and above. If you are using MySQL 4.1+, you definitely should rebuild you own lsphp binary.

That's because the AuthUserFile is double quoted. The fix will be in 2.2.1

You can try: <uri>exp: (.*)/portal/(.*)</uri> Only drawback is that PATH_INFO environment variable will no longer be set. If you code depends on _SERVER['PATH_INFO'] you can consider use <location>$DOC_ROOT/$1/portal?path_info=$2</location> _REQUEST['path_info'] is what...

Amr, You can take a look at the configuration of our demo Wordpress site. http://www.litespeedtech.com/products/webserver/demo/ No need to run apimport.sh now, just let LSWS use Apache httpd.conf directly. http://www.litespeedtech.com/docs/webserver/config/general/#loadApacheConf

Thanks. It will be addressed in release 2.2.1.

I knew the PHP4+PHP5 setup will cause problem. :-) We will address that in 2.2.1 .

No problem. :) Actaully, LSAPI can be started exactly the same way by using a FCGI spawner. However, we are thinking about a better solution by installing LSWS + ruby LSAPI on each node. As LSAPI processes are managed by LSWS directly, there is no need for spawner and spinner anymore, just...

Any chance to try it out? Any update? Thanks!

We plan to build 64 bit binary, probably for the Enterprise Edition only. :)

To run 32bit executable under 64bit FreeBSD, you probably need to install the 32bit compatiblity libraries. http://ftp.sk.freebsd.org/pub/FreeBSD/releases/amd64/6.1-RELEASE/lib32/ We have never done that, so, please keep us posted if you try that. :)

Using PHP_LSAPI_CHILDREN will start all PHP processes statically, so it may handle the traffic surge a little bit better, but it will not solve the load spike problem completely. You can set "Dynamic Requests/second" to smooth the traffic surge a little. Better to found out exactly what...