I deal with a lot of big files on a regular basis. Operations on these files (copy, move, secure delete) take a long time due to their size. I am often ready to do something else when Opus is still working on the last thing. Opus is multi-threaded and will let me do pretty much whatever I want while existing operations are still ongoing, but adding another secure delete operation to a drive that's already being taxed to 90% throughput capacity only serves to slow both operations.
I'm wondering if there's a way to queue such operations rather than have them occur immediately? Opus would add the next "copy" to the end of the queue and get to it when things ahead of it in the queue have finished. This would obviously be a secondary method of operation since it would not be the behavior most people would expect.
I think I could emulate this type of behavior for the secure delete by using a file collection. I have no clue how to approach it for any other type of operation.