Search results

Did the data and conf directory got created under /export/home/syn/awstats? If yes, please list all files under those directories. Did awstats.maverick.conf get created? Can you do something like truss or ktrace, which ever is available. like truss ./lshttpd -n "-n" tell lshttpd not to daemonize.

Do you have the core file in /tmp/lshttpd? Please exam it with GDB, post the result of "bt" command. What is the name of that vhost? Thanks.

%{ENV:variable} is available but %{ENV:HOSTNAME} is not, it has to be set explicitly. And you cannot use it in the matching pattern.

most configuration files are in lsws/conf directory. Should build your own PHP binary.

This has been fixed, will be available with the final 3.1.1 release to be announced.

You can rename the old installation directory, then start from scratch. The old configuration files can be copied to your new installation.

It works for us, maybe try it in another .htaccess. "Options" override must be allowed. Maybe something special in your .htaccess file, please send us your whole .htaccess for analysis.

"sessionid" has been used as a rewrite variable in a rewrite rule in a .htaccess somewhere. maybe grep it.

Using a rewrite rule is the simpliest solution.

I could not reproduce this with a default FastCGI PHP 5.2.2 build with "./configure --enable-fastcgi", tried the php.ini-dist and php.ini-recommended come with the package. test code: hello.php <?php print "hello,world"; ?> Both leading and trialing space has not be removed when run it...

Whether to ignore the trailing white space is completely inside PHP engine, LSAPI has no control over it, like you said, it might be controled by a configuration in php.ini. You have to use the same php.ini when you compare the output of FCGI PHP and LSAPI PHP. Just use command line option "-c...

1) I think you need to turn output buffering in php.ini to avoid the "can't start headers, output already started errors". It really is the PHP internal, have thing to do with LSAPI, LSAPI just do what have been told by the PHP engine. There is nothing to worry about response headers when...

Yes, you can do both, VH rewrite rules is more efficient. I think there is a better choice for your needs. On the image node, you can set "Enable Scripts/ExtApps" to "no", this option is stored in the server configuration file, so you can use different a value for your image node and content...

You'd better building your own PHP binary, just follow tutorial in our wiki. It is the only way to get it up-to-date as early as you can. Make sure to uninstall eAccelerator before upgrade PHP to another version, then install it again after the upgrade.

What was the load before switching to LiteSpeed? If it getting worse, must be something wrong. Are you using control panel, how many php processors are in use? "ps -ef | grep lsphp", maybe your vB need some tune up.

First, you need to clear your browser's cache. The easiest and probably the most efficient way is to add a rewrite rule at vhost level to blocked, should avoid using FILES in htaccess when possible. "SecFilter" is more expensive than a rewrite rule.

Just download 3.1.1 package again.

PHP 4.4.7 has been released, it might be fixed.

This has been fixed in updated 3.1.1 release package. The "ErrorDocument" directive has been verified to be working.

That error is normal on Linux 2.4 kernel. You need to follow our trouble shooting procedure in our document first.