[Tony]

Originally Posted by mistwang

When you build matching PHP from WHM, the PHP will share the same php.ini as Apache mod_php. With LSWS admin console, you have the flexibility to specify the location of php.ini .

To use the same php.ini or separate one is up to you. Some user may have difficulty to keep two php.ini in sync, so, we opted for using one php.ini .

Throwing this up on a semi production environment now and I was hoping to just not do the hack up I did while testing. I'm close except for one thing.

It seems with the PDO modules the build matching library doesn't work out to well. You end up with the litespeed version being unable to load the pdo modules. At least in my environment that seems to be the case. If you drop in the ones generated from the build then you end up with the old php being unable to load the modules. This is a problem if you have say the CLI PHP still available.

So how can one specify a different php.ini via the admin console? I can't find where that's an option.