Errors serving files that have been recently replaced - incorrect stale cache?

[gingerbeardman]

1. I have some files on my website, a PHP site through EE
2. I copy a new version of a file, any type of html/image/pdf/xml/txt/etc
3. When I access the file shortly after replacing I get an nginx server error

Other errors might be truncated file so I can't see all the text (html/xml/txt), or complaint about the end of the file being reached prematurely (binary file).

This makes me think it is a stale caching issue, and somehow the cache does not notice that the file has changed.

Workarounds

• wait a minute or so and the error will go away (I guess the cache finally goes stale)

How can I prevent these errors? Or speed up the cache going stale?

Thanks

edit: related old report of mine #1798

[gingerbeardman]

Apparently...

The root cause of the messages in question is non-atomic file
update. Somebody on your system edited the file in question
in-place, instead of re-creating it with a temporary name and then
using "mv" to atomically update the file.

It seems that disabling open_file_cache, will stop these errors.

But it seems that I should look into my file transfer app to replace the file in a better way.