4.1rc2

[DraCoola]

That's would be great!
But... is it safe to use another php version which that different than php version in Cpanel list?

[mistwang]

Just use the same PHP version.
easiest way is to overwrite the /home/cpeasyapache/ls.src/php-5.xxxx/sapi/litespeed

with the new code,

Then type command "make" under /home/cpeasyapache/ls.src/php-5.xxxx

copy php-5.xxxx/sapi/litepseed/php to lsws/fcgi-bin/lsphp-5.xxxx

[DraCoola]

Seems cool....
Many thanks for your instruction, George.
I will do it now!

[DraCoola]

Originally Posted by mistwang

Just use the same PHP version.
easiest way is to overwrite the /home/cpeasyapache/ls.src/php-5.xxxx/sapi/litespeed

with the new code,

Then type command "make" under /home/cpeasyapache/ls.src/php-5.xxxx

copy php-5.xxxx/sapi/litepseed/php to lsws/fcgi-bin/lsphp-5.xxxx

Already done as your instructed.
But nothing happen
Still showing for lsws only on top command and whm Main >> Server Status >> CPU/Memory/MySQL Usage.
Did I should still rebuild php again from litespeed whm main screen?

[DraCoola]

I thought I know what I am missing :

root@xxx [/home/cpeasyapache/ls.src/php-5.2.11/sapi/litespeed]# cp php /usr/local/lsws/fcgi-bin/lsphp-5.2.11
cp: overwrite `/usr/local/lsws/fcgi-bin/lsphp-5.2.11'? y
cp: cannot create regular file `/usr/local/lsws/fcgi-bin/lsphp-5.2.11': Text file busy

How to copy that actually?

Thank you so very much

[DraCoola]

UPDATE :

It is worked!!!
I have to switch lsws to apache first
Some scripts running under php are showed now.

Awesome, but still nearly perfect...
Using top and then type c will show php process under the user :

lsphp5: /home/username/public_html/folder/index.php

Not all of lsphp5 pid bring the output like that above, but this is seriously help much

[colorprint]

Any progress on the 4.1 ?

[mistwang]

Originally Posted by colorprint

Any progress on the 4.1 ?

Still working on it.

[robdiablo]

Originally Posted by mistwang

Still working on it.

The Release Candidates have been working fine for us so far so we are in no hurry to see the final 4.1. I'd rather have you finish it without bugs and being complete than introduce a product that could set us back some. However, you should keep your customers informed on status updates even if you don't have a time line set just so they know you are still hard at work! Thanks for taking the time to create a great product.

[anewday]

Don't release another RC until the the Apache-style real-time stats are done.