the rule can be found through
lsws admin console->Configuration->Server->
Request Filter->XSS attack->just disable it
restart lsws. see if the issue gone.
since your are running WHM/cpanel, apache's httpd.conf is read and parsed.
won't work in this case.
please google "apache log rotation" for solution, and I believe cPanel has good solution for it.
please refer wiki:
http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:multiple_phps_in_control_panel_lsws
default php not mean all .php to use this lsphp5, it can be overwritten.
follow the wiki, if any question or unexpected result, paste here.
per the output, lsphp5 is just a symbol link, the lsphp you built lsphp-5.3.8,lsphp-5.2.17 are all there.
when you want 5.2.17 as default lsphp5, after build 5.3.x, run
#cd /usr/local/lsws/fcgi-bin
#ln -sf lsphp-5.2.17 lsphp5
then restart lsws
in one of test machine:
#groups lsadm
lsadm : lsadm nobody
so lsadm is in nobody group.
in your case, /home/user/public_html/example.com/config/file.xml
I think only config and file.xml need owned by lsadm, other parent directories can be owned by other users as long as their permission is...
this is a typical for php-heavy app. same issue when you run wordpress under apache or nginx.
the solution is to install a wordpress-plugin, like wp-supercache. It'll reduce the load much and serve smoothly under high traffic.
yes, please be more specific about your issue. if there are many issues, just focus 1 issue which you think most significant.
what's your current problem? can't see it in your posts.