4.0b3 release

[mistwang]

Finally, here comes 4.0b3 release.

New features are:

• mod_security 2.x rule support
• Improved mod_security audit log, compatible with cPanel mod_security plugin.
• reorganized real-time status page
• Large file support for 32bit Linux
• All bug fixes from 3.3.x releases

To enable cache for vhost configured through Apache httpd.conf, directive

CacheEnable ...

should be set for the vhost or from .htaccess


only linux package is available now

i386-std package
http://www.litespeedtech.com/package...6-linux.tar.gz

i386-ent package
http://www.litespeedtech.com/package...6-linux.tar.gz

x86_64-ent package
http://www.litespeedtech.com/package...4-linux.tar.gz

[anewday]

Great work! How many betas before the final version?

PS any updates on this?

[mistwang]

It will be addressed along with the new server status page. This release is only a make up, did not change the way it works or add something new.

We'd like to have another beta release, then go through two or three Release Candidate releases before the official release. Hopefully, we will move faster than current pace.

[PSS]

Will the Release Candidate versions be good for production servers, or the Gold only?

[mistwang]

Release candidates should be pretty stable. For the beta releases, only the new features are not considered stable, as it has not been widely tested.

[kc8yds]

i installed this on both of my servers and got these errors after it started running & it was really slow loading the panel

2008-11-23 21:54:58.419 WARN [AutoRestarter] forking too frequently, suspend for a while!
2008-11-23 21:56:02.306 WARN [AutoRestarter] forking too frequently, suspend for a while!
2008-11-23 21:57:03.414 WARN [AutoRestarter] forking too frequently, suspend for a while!


installed on centos (5) no control panel -- same on both servers



if you need any other info just ask

[closet geek]

Now that mod_sec v2 compatibility has been added I'm keen to test it. We are using LiteSpeed directly using it's own configuration files i.e. not importing from Apache. How do we set each VirtualHost to use a global mod_sec.conf rules file?

[mistwang]

Originally Posted by closet geek

Now that mod_sec v2 compatibility has been added I'm keen to test it. We are using LiteSpeed directly using it's own configuration files i.e. not importing from Apache. How do we set each VirtualHost to use a global mod_sec.conf rules file?

Just set the security rule at server level.

[mistwang]

Originally Posted by kc8yds

i installed this on both of my servers and got these errors after it started running & it was really slow loading the panel

2008-11-23 21:54:58.419 WARN [AutoRestarter] forking too frequently, suspend for a while!
2008-11-23 21:56:02.306 WARN [AutoRestarter] forking too frequently, suspend for a while!
2008-11-23 21:57:03.414 WARN [AutoRestarter] forking too frequently, suspend for a while!


installed on centos (5) no control panel -- same on both servers



if you need any other info just ask

The best option is to let us login to your server and take a look. If it is not possible, you can send us the core files under /tmp/lshttpd/bak_core directory.

[closet geek]

Originally Posted by mistwang

Just set the security rule at server level.

So rules can't be imported from a file they must be manually added to the server's overall Filter page?

Thanks.