Search results

There is a thread in webhostingtalk about PHP 4.4.6 + Apache, http://www.webhostingtalk.com/showthread.php?t=601125 We are investigating the user dir issue.

Same thing will happen with Apache mod_php.

As I knew, it is a bug in PHP 4.4.6, but PHP team won't fix it, you can check PHP's bug reports.

cPanel override "open_basedir" for each virtual host in httpd.conf, it is honored by LiteSpeed, Please check it via a phpinfo page.

That's because some contexts do not have a handler configuration. Those errors has no harm, but anyway, package has been udpated to fix it.

The server should expand the variable, forgot to do that for context handlers. Fix is in 3.1.1, you can change version number in the download link to get new release.

Hiding the server identity is available with our Enterprise edition. :)

That's correct. the load balancer in LSWS is biased toward the first worker app when two works has equal load. Load is calcuated as <ConnectionsInUse>/<MaxConn> for each backend application.

LSWS will rotate the access log for apache vhost when the size reaches 2000MB to avoid server crashes. LSWS does not delete old log file when rotate it. We are investigating a problem related to access logging.

The watchdog process does not do much things after loading the configuration, rarely crash once started. Yes, you can have SMF watch the watchdog process. That's what I am going to suggest as well.

I am not familiar with Solaris 10 SMF function, but I think it is just a Process watch dog, which start another instance if the previous instance is dead. Our "Auto Restart" is far superior than any third party watch dog implementation, as it simply fork a child process with everything has...

Please download 3.1 freebsd package again, we made a mistake when we built the package.

update checking and awstats update are done in the watchdog process, if "auto start" is set to "no", those steps probably is skipped. Maybe we should remove this option from our web console, and let it on all the time.

"Auto restart" should be "Yes" for most setup, it helps restoring the service immediately if one lshttpd crashes. To me, there is no down side of doing this.

Just run install.sh and select "upgrade", same result as doing it from web admin. Maybe the awstats problem was fixed as well.

OK, good. Is there a dedicate access log file for that vhost?

try the following configuration: Max Connections: 2 (maybe 3 is ok) Connection Keepalive Timeout: not set Max Idle Time: not set Since you set Max Idle time, the ruby process will be stopped if idle for a while, when a new request comes in, it will take a lot effort to initialize the...

How about "/export/home/syn/", user's home directory usually has strict permission masks, that is why I said "along the path of ...".

The typo is fixed, thanks. "$VH_NAME" is required in template configuration, it is to avoid multiple vhost level external application with the same name being defined when multiple vhosts has been created based on the template. Something may break when it happens.

Maybe it is a permission issue along the path of /export/home/syn/www_secure/awstats/, the user that LSWS run as does not have permission to copy the file over.