Search results

For a remote ExtApp, you just leave all configurations below "Auto Start" unset. For example: Name remoteLsapi Address 127.0.0.1:4567 Max Connections 10 Environment <not set> Initial Request Timeout (secs) 60 Retry Timeout (secs) 0 Response Bufferring No Auto Start...

Yes, you need to add "&" at end of the command line to put it to background. Maybe add "nohup" to the command line as well, nohup ./lsphp -b ... & It will not start 15 processes at beginning, a new PHP process will be forked when there is a new request comes in.

OK, thanks. We will investigate.

PHP and MySQL optimizations should apply to all setup no matter which server is used. LSWS comes with pretty optimized default configuration, maybe only a few minor changes are required, we have it covered. :)

I guess it should be a permission problem if the directory already exist. You can try change $VH_ROOT/html to "/webs/mydomain.com/html", see if it will help.

Yes, opcode cache caches compiled PHP scripts, so there is no need to compile the script again and again. The real world improvment is depends on how complicate the PHP script is. The most common opcode caches are "APC" and "eAccelerator" now. Google on those key words can give you more...

Thank you for sharing your experience with our product. Hope you will become one of our happy litespeed enterprise customers soon. :) If you don't mind prompting a commercial product, please help us spread the words in the vBulletin community. Thanks! ;)

"Server Name" is intended for this purpose, you can change it from default "lshttpd". Maybe we can set it to "uname -n" during installation.

BugZilla is written as plain Perl CGI, so it should work well with LiteSpeed. In addition to the step in our cPanel guide, you need to add a script handler for ".pl" at server level, just use CGI as handler. restart LiteSpeed, it should work. You can try our persistent perl daemon to improve...

I have not found any open source package does not work well with gmake. Maybe some sun packages require make, but I never have any problem with gmake.

fastcgi settings should be removed from configuration. Only one SAPI extension can be built.

I think should let "make" an alias of "gmake" and override the make comes with solaris. Both phpinfo and -v should show it is "LiteSpeed" SAPI if it is successful.

You need to install GNU m4/gmake/autoconf/gcc, make sure those tools is used instead of sun's. You can try a different version as well.

If you set "Secure" to "Yes", you need to specify SSL key and certificate as well.

Better use access log for this purpose, or turn on awstats integration. 404 message is at "INFO" or "DEBUG" level.

Correct. Easier than that, just run installer and select upgrade, no downtime at all.

We will when we get a chance.

Answer to your question. http://www.litespeedtech.com/support/forum/showthread.php?p=4646#post4646

Yes, you can do that. You should be able to do whatever you did with lighttpd with LSWS. :) When the backlog of TCP server socket is not full, the pending connection will be held in the backlog, when the backlog was full, more connections will be refused. Linux's TCP backlog can hold upto 200...

Not an error level message in LSWS.