Search results

Earlier version of APC has issue with SMP server, should have been fixed in current release. It is strange that it works on command line, but not from within web server. Please double check the phpinfo.php output, see if php configuration file /opt/lsws/conf/php.ini has been used. it might...

Is it at server level, or at vhost level? It might be a bug in the new webadmin interface. We will check.

I think the problem probably is the namevirtualhost, if you only host one web site on one IP, you don't have to use namedvirtualhost. And in the <VirtualHost ...> directive, see if you can get rid of the port number only leave the IP address. The problem probably is because LSWS send Apache...

Yes, 2.2.6 may not work well, latest 3.0RC1 works.

command line php is from the Linux distribution, lsphp bundled in LSWS package is 4.4.4 . You can use APC instead of eaccelerator which included in the package. you may need to build your own php and eaccelerator.

Firefox blocked access to port 79. Not sure about the IE error. Is port 79 blocked by firewall? open a dos prompt and try "telnet <ip> 79" see if you can connect to the server. If you can, it probably is something wrong with the httpd.conf. 3.0RC1 package has been updated to address a...

3.0RC1 package has been updated to address the mailman issue, only mailman will run with group "nobody". The bytes log problem should be addressed as well, probably a miscounting of incoming bytes in certain situation.

Yes, LSWS will change to port 8080 after restart since it uses the apache configuration. Like what I said in last post, configure apache to use port 79 and 442 for SSL, set "Apache port offset" to "1", so LSWS will use port 80 and 443. The external app address should change to "localhost:79" as...

Are admincp and chat in the same directory? Please double check your document root configuration, maybe you have two vbulletin installations at two locations?

Yes, I think so. Is LSWS using Apache's httpd.conf? If yes, you need to create a backup copy of the httpd.conf for LSWS. Or, you can use "Apache port Offset" configuration to let LSWS run on the standard port 80 while apache on port 79 or something.

For example, 1. run apache or port 81 or whatever port you'd like, just not 80 2. define a web server external app, address should be "127.0.0.1:81". no need to set "environment". 3. add a script handler for suffix "shtml", using the web server external app as handler. If can be done at server...

Is there a "chat" subdirectory under the document root of www.disboards.com, is there anything like index.php under chat directory? Chat is using php3? index.php3 need to be added into directory index setting and php3 script handle need to be added as well.

Actually, you should let lsws forward request to .shtml to apache via the reverse proxy interface. it should work better this way. :)

For security reason, LSWS uses a random port between 7000-8000 for that purpose. Each time lshttpd starts, the port will be different.

SSI is not supported in LSWS.

Answers to your questions: 1) Yes, it works, but probably will not bring the best out of it, but should be much better than using Apache. 2) LSWS comes with php4 binary, If you want to use PHP5 or any other modules not in the prebuilt binary, you need to compile your own php binary, if you need...

There are work arounds with 3.0 Enterprise edition, but not available in standard, unfortunately. Why not let pound log it?

Thanks! Please try "lsws/admin/misc/rc-inst.sh"

For the mailman suexec, does apache treat it specially? I just wonder. We can treat certain CGI script specially, like you said, only force group nobody for it. However, I did not see forcing a group nobody for all CGI scripts is a bad idea if permissions has been set properly. For the bytes...

That should be the administration port used for communication between the web admin interface and the server process.