Search results

Thank you very much for taking the time to provide all of these answers. :-)

Strange, I did try "Switch to Litespeed," and it didn't resolve the problem. I have never set LiteSpeed to work in offset. However I did restart the VPS and the problem went away. But I wish I knew why it happened.

I have LiteSpeed set up as an Apache replacement. So, normally, the LiteSpeed WHM plugin gives me the option to switch between the two. But now, I see: Why are they both running, and what is the proper way to resolve this? Thanks, Mark

Are you running cPanel, and did you compile PDO using EasyApache? There is apparently a bug in regard to this with PHP 5.3.x and EasyApache. If this is your case, I can provide the fix for you. Mark

Thank you. I hope someone will be willing to answer a few followup questions. There are so many pieces of information on eAccelerator available, it's hard to put them all together. 1) I understand that the use of 1MB shm setting is to force eAccelerator to use the disk cache as much as...

Update: We're seeing the 503s with the default permalink setting. When we change to another setting (e.g., %category%/$postname% or virtually anything similar), the 503s go away. Some users, however, may want the standard setting. How can this be made to work with LiteSpeed? Thanks, Mark

We are experiencing this too on one server (running 2-CPU) but not on another (running VPS). Any fix?

Thank you. On a system with 16 GB RAM (Running LSWS 2-CPU), what size would you recommend setting for /dev/shm?

Is it okay to use the gotroot rules in the current version of LiteSpeed? I think I saw you say elsewhere that they work, but in this thread you suggest using mod_security 1.9 or 2.0/2.1 rules. (I believe gotroot are 2.5.) Thanks, Mark

Thank you for the clarification. :-)

Can you clarify...it is compatible or is not? (The "No" in your answer makes me wonder if you meant to say "No, it is not compatible..."). Thanks.

One of the gotroot rulesets requires mod_sed. Is this compatible with LiteSpeed? It is not part of EasyApache so it needs to be installed separately. If this is compatible with LSWS, what is the proper procedure for installing it and having LSWS recognize it? Thanks.

We are using the gotroot ruleset, and we would not like to revert to anything less secure than that. Will there be problems if we keep using those rules? When is 4.1 due out? Thanks, Mark

Hi, If I am running with mod_security and the Gotroot rules, should I also enable LiteSpeed request filtering? In other words, is that setting required to activate mod_security, or is it a separate thing that will interfere? I want the maximum protection, but I want to make sure everything...

LiteSpeed, can you please answer the questions I've asked: How secure is LiteSpeed now? (In other words, how much of the mod_security functionality is missing?) When will additional security be added? When will LiteSpeed offer the full protection currently offered by Apache + mod_security...

Thank you for the clarification. I had heard that it was necessary to install EA separately, so I am glad this is not the case. In my situation (suPHP), which EA cache scenario would you recommend (/dev/shm, etc.), and how often to clear the cache? Is there a certain cron directive you...

To install eAccelerator, can I just add that option in EasyApache, and then build the matching PHP binary? Or do I need to do something else? Thanks, Mark

It's your choice. You do not need to license the same number of cores that your server has. The LiteSpeed license refers to how many cores will be used by LiteSpeed itself, but not by other apps such as PHP and mySQL. So, with your eight cores, I would recommend a two-core or four-core LiteSpeed...

Thank you. That link shows configuration after installation...is there a definitive guide to installing eAccelerator? I am confused about using the prebuilt binary (how to do that if I have already built a matching PHP binary). Also, we will be using WP Super Cache. Do we also need an...

I also read this: Is this true? We run mostly WordPress, but we also need suEXEC.