Search results

rewrite rule in .htaccess has to remove the leading "/", it is called rewrite base. RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(main|main\/)$ index.php?sec=main [L,QSA] #gallery RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(gallery|gallery\/)$ index.php?sec=gallery&tab=0 [L,QSA]

should be fine.

We can fix the WHM plugin if can get access to a FreeBSD server to play with. cPanel + FreeBSD is not popular. As for native build for 7.0 and 8.0, I am not sure. We already got 3 packages for freebsd, while only two packages for Linux, if support 7.0 and 8.0, need to add 4 packages, just too...

You can increase the "Max connectons" of lsphp5 external app. There might be problem with DB SQL statements, which lock the table for long time, and block all other SQL query, thus all PHP processes hang. Use command mysqladmin processlist to check active SQL querys when you experience the...

xcache does not work very well with PHP suEXEC. If you do not use PHP suEXEC, you can continue using xcache.

You can disable it by remove administrator's email from LSWS web console. But you'd better figure out why WHM kill LiteSpeed with signal SIGKILL.

That require you to create lsphp external app for that user at server level, and configure the script handlers in those vhosts to use that app.

find the right rpm that contain "ab" command. Or build Apache from source.

Yes, eAccelerator is recommended.

I will PM you instruction on how to retrieve call stack information from core file.

is freebsd core dump enabled? If enabled, can you please locate the core file, check the core file with GDB. For compile PHP with GD, maybe there are multiple GD Lib installed, maybe the wrong one was used. Likely cPanel installed its own Lib, like with libcurl. You can check the config.log...

Updated 5.0b2 package, should have addressed this issue.

Anything in /usr/local/apache/logs/error_log ? LSWS should start a new child process immediately when one child process crashed.

install apache. :)

That's fine. we have done some update on our license management system.

http://www.litespeedtech.com/support/forum/showthread.php?t=2016&highlight=freebsd7

No, it is not related to PHP LSAPI, but PHP internal errors.

If you configure per user php.ini, the global php.ini will be ignored for that user, so it could be a security concern for shared hosting environment as you lost the central control of php.ini.

It works as expected then. :) You can override the php.ini in main httpd.conf <virtualhost ...> section with php_admin_value. Per user custom php.ini does not work by default, search for "PHPRC" if you want to use per user php.ini.

Is that function listed in php.ini disable_function configuration?