LSWS uses the same php.ini as Apache (you need to enable Matching PHP integration from LSWS cPanel/WHM plugin and build matching PHP in LSWS)
No, LSWS standard configuration should handle medium-loaded server just fine.
There is no need to change Apache server configuation. LSWS is a drop-in replacement of Apache.
No, LSWS understands Apache configuration and just behave the same way as Apache (as a drop-in replacement)
yes. There are 5 levels of error log, ERROR/WARNING/NOTICE/INFO/DEBUG. if you set to ERROR, only critical errors are logged.
You can turn keepalive on/off at admin console after installation. either works well under litespeed. Since litespeed is event-driven, as server admin, you needn’t worry about rest parameters any more and performance is much better.
LiteSpeed does not care. LiteSpeed use our own LSAPI PHP, which combines all the advantages of mod_php (DSO), FCGI, suPHP, multiple version of PHP can coexist. LiteSpeed does not care what PHP is used in Apache, our PHP solution can do everything that the most complex Apache PHP setup can do, even be able to something very difficult to do in Apache, like using 5 different versions of PHP at the same time.
Once matching PHP is built in LSWS, the same version of Zend/ioCube (in Apache) will be used in LSWS.
Yes, LSWS honors Apache Settings as mentioned above.
No, Litespeed is not vulerable to the Range header attack, it is due to poor implementation in Apache.
No, LSPHP (with PHP suEXEC ⇒ on) work just fine.
Yes, they are working with LSWS right after they are added in WHM. Just like as if Aapche was used.
Yes, they are working with LSWS right after they are added. Just like as if Aapche was used.
It is because httpd is disabled in cPanel (cPanel/WHM ⇒ Service Configuration ⇒ Service Manager ⇒ httpd (Web Server) unchecked for Enabled). Need to have Enabled checked.
See this for further troubleshooting steps.