Search results

No, you do not. You don't license LSWS based on the number of CPU's on your server, you license based on the number of CPU's you want to use. We have many 4 core servers with 2 CPU's licenses. This leaves 2 CPU's available for PHP, MySQL etc.

So when will 4.0.10 be on the auto-update then :D

@mistwang, I'm not sure that we're ready to upgrade to 4.x yet. We need to see a bit more stability in that version. What is really throwing us is that it's not consistent. Things will be fine (no long restart, no high load) for a bunch of domain adds then 'poof' one will just tank the...

Nope, then these are not big :-) They are only about about 25K lines. It's just very inconsistent. Sometimes it works fine, no load etc, the next time it spikes. The biggest problem (of course) is that you can't control when it will happen. Clients add add-on/sub-domains at any time...

We've had just about no problems with LSWS working with .htaccess files. Might help if you tell us a bit more about what is in the .htaccess etc.

Hello Tony, That is not what I want to hear. Define 'big'. Number of lines in httpd.conf, number of hosts? One of the reasons for using LSWS is having more sites on one server. If LSWS dies with bigger httpd.conf's that kind of kills the purpose. Any know work-arounds?

Any thoughts on this one? This is beginning to become a serious issue. When I set get added/add-on gets created the server load can sometimes spike from a normal 2 - 3 to 20 - 30 for 5 or 10 minutes. This is beginning to cause serious problems.

Yea, I saw that in the 4.x forum. I'm still not sure 4.x is stable enough for us :D

I'm not sure this is a LSWS problem, but I'm attacking it from all sites. We create cpanel accounts via our billing system. It uses the xml-api to create the accounts. The account creation process is very (very, very) slow. If we manually create the account it appears to be the 'restarting...

We've been holding off on upgrading to 4.x. Things seem to be stable now so I just wanted to find out: - If we auto-upgrade (via LSWS web admin) can web swap back to 3.x if we run into issues? - Does anything else need to be upgraded (like PHP)? TIA

The problem (for us at least) was that Fantastico was not letting WordPress actually run it's test, they were just building the database with the values from their server. I hope that makes sense.

@mistwang, At least with Fantastcio it was a double compression issue. Because they were 'setting' the value rather than letting WP check it. Basically WP was doing the content compression and then LSWS was doing it a second time.

We actually tracked the issue down to the way that Fantastico installs the db. There is an optino that gets set 'wrong'. Here is the fix: - You'll need to go into the wp_options table - search for a row where the option_name = 'can_compress_scripts' The option_value for that row will be...

No one????

We're building up a very large quantity of error_log* and stderr.log* files. Is there anything in LSWS that automagically cleans these up? I'm assuming there is no issue with just rm'ing the older ones? TIA

Worked perfect. Thank you.

Is there any way to disable gzip for certain file names (globally)? The latest version of WordPress (2.8) creates stylesheets like this: link href='style' href='http://blah.com/wp-admin/load-styles.php?c=1&dir=ltr&load=dashboard,plugin-install,global,wp-admin&ver=abcdefghi' The output...

OK, I must be missing something, but I can't find it. We have a client that has a very long running PHP process. It's part of their shopping cart application. I've updated the max execution time in php to be about 5 minutes. In LSWS (under config, server, security) I have the cpu soft limit...

We've got 100 meg of "stuff" under /tmp/lshttpd/swap. Other than tmpwatch is there any automated way to clean this up? LSWS does not appear to clean it up. TIA

Can you post the command line that your cron is running?