Search results

With localhost, there is no network delay, you will not notice the first URL, put your mouse over the link, you will see the target link from status bar. You can check the response with firebug, it will show what happened. The second one was eventually redirected to...

Please check stderr.log see if anything logged. Will it work if you take the "Set UID" bit off?

find out the location of php.ini from a phpinfo() page, then update the php.ini

seems linux still lack the ability of per user CPU usage limit.

Our installation service is extra. You can try to hire an admin off webhostingtalk for less if you could not handle it yourself.

Maybe another permission problem, it should be like -r-sr-xr-x 1 root root 11680 Dec 19 20:59 lscgid.3.3.24

It should have been fixed in the latest release.

We can have your serial number unchanged. so, you do not have to do anything.

I think you missed the set uid bit on lscgid.3.3.24 when you replace the binary. so suEXEC does not work any more.

use PHP suEXEC, and resource limit policy on Linux, you can limit memory and CPU usages for each user account, for connection, you cannot do that at per user level, however, our anti-DDoS feature should address part of the problem.

Answers to both of you questions are "NO". you have to configure each directory individually.

If you are using monthly license, just stop renew the 1-CPU license, and order 4-CPU license when the old one is about to expire. We can also give you prorated credit if your 1-CPU license have time left when you order the new one. For owned license, we will prorate your existing license and...

If you use apache httpd.conf, You can use php_admin_value open_basedir "..." with <directory> directives in vhost configuration to limit access. If you use LSWS admin console, just add a context for each project, and apply above configuration via "Apache style configuration".

found a bug in lscgid, please PM me your email and the OS/LSWS release you were using, I will send you updated lscgid binary.

Still not sure what exactly is the problem, but I think it is a bug in the cache proxy not LSWS, it should be able to take two "Vary" headers. Maybe the easiest solution is to use LSWS 4.0rc1 cache function and get rid of the cache proxy.

mv /usr/local/apache/bin/httpd_ls_bak /usr/local/apache/bin/httpd

You should check error.log and stderr.log. Usually, it is caused by insufficient memory limit when you use xcache or eaccelerator etc. search the forum, there are too many posts about this.

Does it hurt if there are two "Vary: Accept-Encoding" headers.

due the log format, cPanel may not able to detect blocked requests. 4.0 release does better job on this. LSWS does not block request ends up with 404, so if you think LSWS should block a request with certain rule, please give an example.

How do you know?