@quags we could introduce a special variable in
directadmin.conf to enable such mode. However I think it only hides the real issue instead of fixing. Could you give me more details why would you like to keep only one instance of
dataskq running?
Even if single
dataskq instance takes quite some time to execute it truncates the task log so that subsequent concurrent
dataskq calls will have nothing more to do. Strictly serializing all
dataskq calls is trivial to implement but could have a very nasty consequences. For example if you start a backup for a huge account it could take hours to finish, with concurrent dataskq disabled all other actions would be stuck until the large backup or restore job gets finished.
If you are worried about multiple backup jobs running concurrently you can limit them to with the
max_concurrent_backups config parameter in the
directadmin.conf file,
link to feature description.