If I'm scanning a large tree and want to pass results to another command before scanning the whole thing, will the ; option do this? From my reading, it seems to, but I want to be certain there's no background caching. If there is background caching, I want to know so I can use for loops instead.
When running find on a few files, there is no delay or strain on the disc. For a script that runs often, and on a long list of files, it can take minutes before find passes the full list to the next command. I want find to only run on one file at a time, and also refrain from searching the target until the previous -exec is completed.