Search results

Please try creating a admin/ directory and put a .htaccess with a authentication realm in it.

You do not need to reinstall the server. 6000 should be enough since it is ont likely that 150,000 files get accessed at the same time. LSWS automatically set the file descriptor limit to 3 * "Max Connections". Your "Server"->"Tuning"->"Max Connections" is 2000 now. If you want a higher...

404.php is a PHP script. Using static HTML will return 404. If you want to use 404.php, you need to set status code to 404 explicitly in that script.

Are you using a script for the custom 404 page? Internally, LiteSpeed does return 404 for static custom error page. Our Rails support uses 404 handler, the status code returned by the script will be used. So, if you use a script for 404 page, you should explicitly set the status code to 404 in...

time limit should not affect PHP though, memory and process limit does, you should check error.log and stderr.log for reasons behind the death of long php scripts.

Yes, if PHP trys to use more resource than the limits.

A NULL pointer has been referenced when dumping the error message. Fixed. The requirement is for security reason, since this awstats update is initiated as "root" user, (changed user id later). Document root for a vhost can be same as virtual host or a sub directory under vhost root. Right...

exam the core file with GDB first. gdb lshttpd <core_file> then bt<enter> Post or send me the call stack back trace.

Please look into "coreadm" command to let solaris dump core file for setuid process, with a core file, we can easily identify and fix the problem.

What kind of server and browser are you using? How many vhosts do you have there? The YUI lib used is a bit slow but it should not take that long.

Found the problem, you need to set "location" to where the java web application located when you define the "/jwchat/" context.

Since LiteSpeed does dynamic spawn for Rails Application, and cost of Rails framework initialization is very high, and your configuration make LiteSpeed to initialize it again and again. That's why you feel litespeed is slower. Reduce "Max Connections" to match the number of Mongrels you run...

The strace ouptut shows that the LSWS started successfully. Was the vhost causing problem taken out from httpd_config.xml when you run the strace? Please remove those core files under /tmp/lshttpd, then try to reproduce the problem, if a new core file is created, email the core, along with...

Self managed mode is perfered as all PHP processes can share their opcode cache. CPU usage and performance wise, there is no big difference.

vBSEO has dedicate rewrite rules for LiteSpeed, please do a Google search first.

Please do "strace ./lshttpd -d", and send the output to bug ((a)) litespeedtech ((.)) com, if you do not want to post it here. Please check if there is core files produced in /tmp/lshttpd or lsws/bin directory. The YUI used in the new admin console has a slow start.

Please consult the README file and a few examples in our ruby-lsapi. Ruby CGI/FCGI can be easily converted to use our LSAPI interface.

ruby-lsapi fork children processes to handle requests. For some reasons, children ruby process has issues when it fork again, like calling popen(), etc. And I believe ruby has fork related bugs in its core library.

You can give it a try. It might work.

It is not recommended, at least for the httpd_config.xml, for other configuration files, the file locations are configurable.