Nikolai Weibull wrote: > I haven't really understood what the problem is (I don't believe that > there actually is one),
There is a non-zero time period between open file and write complete content. Because vim truncate file while opening (O_TRUNC), another process which would like to read it can hit in the moment when file will be empty. > but would opening the file exclusively solve the problem? Do you mean O_EXCL flag to open syscall? It doesn't protect against such a situation. It only guarantee that file doesn't exist prior to call open in atomic manner. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
