I'm making the same changes to all sites, resetting the php.ini settings and Apache directives. On Save, the jobs are queued and processed. Each Save requires an Apache2 restart. All processes are killed, the service is deactivated, and Apache is restarted. This process precludes rapid execution of operations. We can't change a bunch of sites because after each one the service is restarted, which interferes with the ability to post a new change to the service. So the process is : make a change, wait for the process, make another change ... That's really painful. Can we temporarily disable the auto restart so that we can make a lot of changes and then manually restart from shell or the UI? If it would be better to do this with SQL queries, is it valid to set the php.ini settings, the apache directives, and the snippets used, and then do a resync? Is it correct that if we just associate a snippet with a site that we can then modify the snippet in the system settings, and on Save that will update all sites and do the reload? That would make this very easy. Thanks! v3.2.12p1