Search results

You can try googling it. it is PHP internal error, probably relate to mismatched header files.

You can have Apache run on another port without really take any traffic. cPanel may not work properly if you remove Apache completely.

suHTTPD need a httpd process for serving static contents, and need to start twice amount of processes even for pure PHP dynamic content comparing suPHP. It is a pretty big scalability issue. I think your lighttpd solution may not able to go beyond couple hundred accounts.

What you want is in the mind of event-driven and perfork server, it has serious scalability issue, imagine when you want to put 2000 accounts on one server, there is going to be too many processes, and forking processes frequently is not a good idea either. We will stick with our current...

Thank you for the suggestion. LSWS' architecture is a single process event-driven non-blocking server for the maximum performance and scalabilities, what you described cannot apply. suEXEC should be good enough as we only need to worry about the security of CGI script, for static content it...

I think it should be a PHP configuration issue, make sure to use the same configuration parameters reported by phpinfo() page produced by mod_php, minus apache related parameters.

It is possible if you just configure LS natively through the web console. It may not work well if you still want to LS read Apache httpd.conf, I would get rid of Apache completely instead of mixing them up if there is no special requirement for Apache.

Thanks for the suggestion, forgot to mention that you can always enable PHP opcode cache by running script lsws/admin/misc/enable_phpa.sh

You can install PHP opcode cache by building PHP binary from the web console. We turn it off from the installer because we do not offer opcode cache binary for PHP5 while most user will use PHP5 and need to build their own from the web console.

We thought Ensim is close to dead after Parallels took over it, so we do not follow up it closely. Glad that Parallels has finally released something. Litespeed should have no problem to support those features if not all of them are supported now. We need to get a sample Apache httpd...

You should be able to override the error document via .htaccess. LiteSpeed's .htaccess implement is the most efficient with cache.

I suggest you to look into the internal redirect to serve static files directly instead of going through PHP. http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed:wiki:feature:internal_redirect

PDF version is not available.

yes, you can.

LiteSpeed just proxy the request as normal no matter the target server is itself or somewhere else.

LSWS does not like the mime type with trialing ";type=entry". Do you really need to add that MIME configuration like that? "application/atom+xml" is fine with LSWS. if the response is generated by Rails dynamically, you do not have to add that MIME configuration at all.

That's correct. We will tell user this function is not available in the web console for standard edition.