Search results

Even without the stat cache, LiteSpeed enterprise is still about 3x faster than lighttpd when serving small file in keepalive mode. You can try it yourself. The impact of state caching should be pretty small and we have no plan to add it yet. :)

Do not over-tune phpLsapi to start too many php processes, LSWS can pipe-line requests to PHP backend when there are more concurrent requests than number of PHP process. 200 should be the maximum, I recommend you try 50-100 first. Running too many PHP process may use too much memory and slow...

You can add a environment variable LSAPI_MAX_IDLE=n n is the maximum idle time in seconds that a child process will be waiting for a new request. Once it is reached, the child process will quit. Default value is 60. When n <= 0, the child process will wait indefinitely. This option helps...

Cpanel uses a global listener for all SSL vhosts, whereas LiteSpeed needs individual listener for each SSL vhost, we need a little time to come up with a clean solution for this. Please stay tuned. :)

Please follow our Wiki to build APC opcode cache, http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:php:opcode_cache If you build your own php 4.4.4 binary, you can just do "admin/misc/enable_php.sh" to turn on APC code cache. If APC code cache has been installed properly...

The command to stop lshttpd is "lswsctrl stop" not "lshttpd stop". Is that for a vbulletin board? You probably set "max connection" for lsphp module too high. usually, 20 is enough for most setup, unless your php scripts take long time to process. First thing first is to make sure a php opcode...

Latest LSWS package for FreeBSD6.1 http://www.litespeedtech.com/packages/2.2/ent/lsws-2.2.2-ent-i386-freebsd6.tar.gz

I added the code in the first post inside a controller class of a test rails application. It works, and the log message goes into log/production.log. I wonder where you put those code to break rails?

Where does the log message go when logging to STDOUT? WEBrink console? I tried your code in a controller, it works, message goes to the production.log.

Just uninstall the ruby package and install ruby/rails from source, it is pretty easy. :)

Don't know why, the Makefile generated by ruby want to build 32bit binary, however, your ruby lib might be 64bit, so link failed. You can manually remove compiler options "-m32 -march=i386 -mtune=pentium4" from ext/lsapi/Makefile. then do "make clean" "make install" under ext/lsapi/ directory.

I don't know exactly what went wrong, looks like a ruby library problem. I recommend you to install ruby 1.8.4 or 1.8.5 from source if ruby is from the centos distribution.

I think it is the best to use LiteSpeed with Cpanel directly. LiteSpeed can use the httpd.conf file generated by Cpanel, you can have your normal vhosts managed by Cpanel and have your Rails account managed via our own web admin interface as there is no equivalent configuration in Cpanel.

There should not be any problem with 2.2.4 standard upgrade procedure. If there is core files under /tmp/lshttpd/bak_cores/, please send it to bug@litespeedtech.com We can take a look at your installation if you don't mind giving us temp root access for little while.

0770 is fine as well, it just give "nobody" write permission to user's directory. Thanks for the link to your howto, we will add some thing in our document.

I put it on our to-do list. :)

It does happen with error.log, as LSWS rotates the error log file for each restart. But for stderr.log, "tail -f" works fine after restarts, at least on my test server.

We currently have no plan on this. :)

You JRUN server need to be configured to handle request to http://localhost/cfmx exactly the same way as request to http://localhost:8300/cfmx, LSWS just forward the original request without changing the "Host" header from "localhost" to "localhost:8300". Maybe your JRUN server require it to be...

Are you using a Enterprise edition, if yes, please contact our sales to address the problem with 2.2.4 release.