Error 500

[kilburn]

That was with old "locking" code. Keep in mind the now we use real locking assets (flock). When flock is called, the function doesn't return until it successfully acquired the lock.

sci2tech Wrote:1. User1 add subdomain -> engine-mgr is running -> ispcp-sub-mng is running and altering /etc/apache2/sites-available/ispcp.conf
2. reseller / admin modify another domain -> ispcp-dmn/sub/als/subals-mngr is running and try to alter same file.
Now if user1 lock engine, second user will not be able to run engine an must wait until a third user trigger engine.

What would now actually happen is:

1. User1 add subdomain -> rqst-mgr is running -> ispcp-sub-mng is running and altering /etc/apache2/sites-available/ispcp.conf
2. reseller / admin modify another domain -> rqst-mngr is run and gets blocked in the "flock()" call until it can acquire the lock.
3. The first rqst-mngr ends, releasing the lock
4. "flock()" call on the second request returns because now it has been able to acquire the lock -> subals-mngr is run and the reseller/admin changes are made effective

See? No gui locking, and still no problem.