Search results

Don't know what exactly is the problem, below is our RubyRunner configuration, you can give it a try. Name RubyRunner Address uds://tmp/lshttpd/rubyrunner.sock Max Connections 10 Environment N/A Initial Request Timeout (secs) 60 Retry Timeout (secs) 0 Persistent Connection Yes...

Have you built and installed the ruby extension? Is execution bit enabled for ruby_runner.rb? For trouble shooting, please check lsws/logs/error.log and stderr.log

You need to add a context for that directory, and set "php_admin_value" there. For example: if directory /webroot/squirrelmail/plugins/squirrelspell/ was accessed with url "/squirrelmail/plugins/squirrelspell/" then define a context with URI: squirrelmail/plugins/squirrelspell/, location...

The php.ini used by the pre-built PHP binary is located at lsws/conf/php.ini, and the path to php.ini should be in the phpinfo page as well.

That's because of the "Files" directive support. Will try to address this in next release. :-)

ulimited. The FAQ need to be updated.

You can use a rewrite rule to set those environment variables. Or, create a dedicated lsphp external application for that vhost, then add environment there.

don't install LSWS to /etc/lsws, as /etc is a system configuration directory, LSWS does not allow serving anything under /etc.

No windows version and there is no plan for it.

It is lsws/admin/html. The permissionof that directory is not the problem, as the install script always try to set right permission for all files it touched. The permission problem is in the parent directories where LSWS was installed to. You should install LSWS install to a system directory...

It might be a permission problem on your file system. Like installing to a user's home directory and start the web server with user "nobody", and nobody has no permission to acess files under that directory.

it is demand driven and working in progress, no definite ETA yet. :-) The client IP should be forwarded via HTTP header "X-Forwarded-For" by Apache, you may have to modify web app code to extract that. Proxying through Apache will not give you the performance advantage provided by LSWS. :-)

Currently, you need to use the VH template if you want PHP suEXEC. We will add a feature to address this later. When run LSWS off apache configuration, LSWS logs bandwidth usage into the same bandwidth log file produced by mod_log_byte in Apache. So Cpanel can calculate the bandwidth usage as...

If you find LSWS has difficulty parsing your httpd.conf, and you don't mind, please send us the section causing problem, we will fix it soon. :-)

When you run Apache parallel to LSWS to test the "Using Apache configuration" feature, you should use "Apache port offset" http://www.litespeedtech.com/docs/ServGeneral_Help.html#apachePortOffset, if you set it to "1", then LSWS will listen on port "81" if apache is on port 80. Make sure you...

If you are using ruby FCGI, remember to turn off "persistent connection" in the dispatcher.fcgi application. With LSWS release 2.1.13, you can try our own ruby interface at http://www.litespeedtech.com/lsapi/

Hi Suxen, If you let LSWS "Using Aapche Configuration File", then you should not import apache configuration during installation, only pick one. I recommend "Using Aapche Configuration File" for Cpanel and you need to add new vhosts for new customers. If you looking at port 8088, you...

sendfile support will be turned on in professional edition in 2.1.13.

There should not be any problem with this. I tried it with different configurations, all works. Have you tried using URI: /path/script.pl ? If URI=/path/ works, and script.pl pointing to the same file, I don't see any reason why it won't work. :-)

We need more feedback to make LSWS/cpanel works better. For cacti or mrtg integration, you can write a simple script to parse /tmp/lshttpd/.rtreport to get data displayed in our web real time status report. :-)