Has any else noticed that Cpanel doesn't understand how to lock the httpd.conf file poprerly on apache when it does an insert (virtual host entry) and a SIGUSR1 (Graceful restart of apache)?

It simply doesn't work. Heres how to test (It doesn't happen everytime).

Create a new account, or add on domain which forces cpanel to do a httpd graceful restart then hurry and add another domain or create another account. It then sends ANOTHER SIGUSR1 (Graceful restart) to apache before the other finishes. The second one tries to read in the conf file before the first one finishes and then apache dies because the conf file was invalid. Then you have to wait 5 mins or so before Cpanels health check decides that apache is down and issues a /scripts/restartsrv httpd. PLEASE PLEASE PLEASE LOCK THE CONF FILE WHILE YOU DO A RESTART. This is such an easy fix. I can't believe we are on 9.2 and still don't have it. THANKS!

We do have about 1000 domains on the server so the startup takes longer than boxes with no users. Without a lot of domains it WILL be much harder to duplicate. LOCK LOCK LOCK!

Matt