Search results

Is the server started as root users? Maybe because insufficient permission. Another possibility is that lshttpd does not execute it at all due to authentication problem, that should be logged in the error.log.

You are welcome. :-) That should not affect ".php", could be a bug, I will take a look. It not easy to support Apache style MIME setting and .htaccess in much efficient manner. ;-) Thanks.

The lshttpd will execute lsws/admin/misc/update.sh when the update request has been received. You can try that script from console, see what kind of error it reports.

Only possible reason I could think of is that the MIME setting has been overriden some where, at context level or in a .htaccess file. The problem cannot be fixed by adding an explicit script handler?

You can check lsws/autoupdate/update.log, but I not sure anything useful to diagnose this problem is logged there. The update package should be expanded under lsws/autoupdate/ directory. Please check the error.log regarding update as well. Another thing to try is to restart the web server...

You can enable core dump the same way for 2.6 kernel from the admin interface. If the kernel is not patched disallowing it, the error log will report "core dump is enabled." when you restart the server.

Which version of MySQL are you using? I am afraid you need to follow our Howto to build your own php binary with the updated MySQL client, the default MySQL client comes with PHP 4.3.x is MySQL version 3.xx client library. I think the error message is pretty clear. :-)

It probably caused by the new error logging code, but I am not 100% sure. That will be great if you can send us a core file, if interested please follow the direction in http://www.litespeedtech.com/bugs.html If you are using a stock Redhat kernel, then forget about it, as the kernel is...

In this week. :)

We will make them dfferent under special cases. For most situation, it is sufficient. It will not be a rewrite rule if implemented as a dedicated feature, rewrite rule is not as efficient. Looks like you do need to create a vhost for apache as well. And similiar configuration can be...

Looks like there are something need a fix in the server as well, will be fixed in next release. Thank you. :-)

The server itself can take command-line options, but the web admin interface won't allow you to add any right now, will be fixed. You can change the configuration file directly. Even command line options are supported, lsws still don't have any idea about how to populate "%Y/%m/%d", and we have...

Right now LSWS treats domain.com and www.domain.com as the same domain name, the leading "www." will be ignored. If you prefer one over another, you can use a simple URL rewrite url to do the redirect right now, no need to create another virtual host. We can add a feature that forces to...

Thomas, Thank you for the suggestions. We plan to integrate with cacti for history stats, just like we did for awstats. Actually, one of user has done that already. In this way you could monitor multiple servers in one place and dump MRTG. ;-) We did not include total requests and...

Yes, you need to rebuild your PHP binary if use PATH_INFO. "--disable-path-info-check" is an awkward workaround for those web servers not passing correct PATH_INFO and PATH_TRANSLATED envs. LiteSpeed follows CGI specs more strickly and do not need this work around.

rotate litespeed log file is as easy as "mv error.log ...", no need for a piped logger, same is true for access log. Piped logger is useful for acess logging because some one might want to log in a DB or something else. We will add virtual host name in error log in next release. It is a good...

http://www.litespeedtech.com/docs/HowTo_QA.html#qa_apimport

We don't do that beacuse we could not think of a compelling reason for this feature. If you can convince us, we will add it. :-)

You can run it any time you want.

The current version of apache configuration importing tool does not handle the directive that includs configuration files under a directory well. However, it does handle individual file. If it is not a big trouble, you can list all configuration files under that directory in the main...