https://github.com/i-MSCP/imsc…ch?utf8=%E2%9C%93&q=chown
Das Ganze während eines Updates im Code auskommentieren?
He is talking about chown command which is run when you change domain name properties. See https://github.com/i-MSCP/imsc…d/apache_php_fpm.pm#L1710
We could just remove recursivity and make the full process optional (to handle case where user maps has been changed).
Will be fixed in 1.2.18.
I'll add a new option --fix-permissions which will tell to the installer whether or not permissions must be fixed recursively. By default, without this option, the installer will no longer fix permissions recursively. That will prevent long running processes on changes (domain, subdomains ...). Right now, the option will be checked by HTTPD server implementations only. In near future, that option will be checked by all server implementations. Of course, on normal run (e.g: when you just change something through the i-MSCP panel interface, the recursivity will be also disabled).
this is a very nice idea. could you add a second option, that fixes permissions but excludes 00_private of domains folder?
In fact, process will be as follow:
On reconfiguration, and if the --fix-permissions option is passed-in, permissions will be fixed (chmod, chown), else, they won't, excepted for known files (those that are part of Web folder skeleton).
Here, that should cover your case: 00_private folder permissions will still be set but not recursively, meaning that permissions on any file/directory in that folder will not be touched if you don't use the --fix-permissions.
I cannot add a new option for all use cases. I bet you can understand that 
thanks, its exactly what i wish! i should have been more precise, like "contents of 00_private" 
A fix has been added in the 1.2.x branch. See https://github.com/i-MSCP/imsc…3df0d261dfd865a3e13789eba
That fix will be part of version 1.2.18.
See also