Search results

should not. but you need restart lsws after you make change in httpd.conf

when using litespeed with cPanel, litespeed will read and parse apache's httpd.conf. you needn't do settings at "litespeed configuration > server > log", just configure settings in /usr/local/apache/httpd.conf as if apache is running.

my test on our cPanle box shows that litespeed support "%v" in LogFormat as well. please check if any other settings override it? I did test on 4.0.17

looks like same issue with you: http://bugs.php.net/bug.php?id=48809 it gives a workaround:--disable-fileinfo

please try 4.1RC3. see if much difference

install a command "patch" apt-get install patch.x86_64 may resolve the issue. "patch.x86_64" may not be exact debian package name. "aptitude search patch" to get the right name.

output of: ls -l /usr/local/lsws/bin ?

has upgraded to 4.0.17 successfully. experienced the "slow after restarting 5 minutes" issue. most likely the php script's issue, but not identified yet.

which web server? apache or litespeed ?

recommend CentOS. other linux server should be ok too.

need improve your lsphp5. 2 obvious issues at present: (from phpinfo()) 1>no php.ini Loaded Configuration File: (none) 2>no opcode cache although built apc.so, but not enable it since 1>

I moved this thread from LiteSpeed Web Server > General to General > Use Cases

current version: Last-Modified: Mon, 18 Oct 2010 04:24:17 GMT looks to be very stable according to tests from various sources. it's a good chance to upgrade your RC3 to this one :)

during the past 30 days, RC3 has some fixes/improvement and a few versions. please update to latest version. see if any difference.

it may be almost useless to use xcache var under php suExec opcode cache is associated with a php process, web server start/stop the php process dynamically. 2 consecutive requests from a user may be served by different php process. that means cached var in previous request can't be referenced...

are the issues for 4.0.17 only or also exist on 4.0.16? can you specify more detail regarding the 503 error.

php suExec enabled or not ?

the setting looks normal -- in general, the default setting is ok and no need to change them. check error.log, stderr.log, see if any related messages there.

check phpinfo() again, if xcache is there. if it's not there, check extension_dir, and check if $extension_dir/xcache.so exists.

check phpinfo(), the value of "Configuration File (php.ini) Path"