On Tue, Jul 31, 2012 at 12:33 PM, Bernhard Voelker <mail@xxxxxxxxxxxxxxxxxxx> wrote: > > > On 07/30/2012 11:20 PM, Mantas M. wrote: >> Some editors, such as Vim with 'writebackup' mode enabled, use "atomic >> save" in which the old file is deleted and a new one with the same name >> created in its place. > > Why's that "atomic"? > I see a race in between the unlink and the creat call. > I'd tend to consider such editor mode "unlucky" for use with vipw. Perhaps I picked the wrong name for it. Some other editors actually implement it atomically using rename(). Meanwhile, Vim has three settings with at least 36 different combinations, some of which copy and overwrite, others rename and recreate, etc. I did find this paragraph in `:help crontab`, however: *'backupcopy'* *'bkc'* 'backupcopy' 'bkc' string (Vi default for Unix: "yes", otherwise: "auto") [snip] *crontab* One situation where "no" and "auto" will cause problems: A program that opens a file, invokes Vim to edit that file, and then tests if the open file was changed (through the file descriptor) will check the backup file instead of the newly created file. "crontab -e" is an example. Seems like I could :set bkc=yes and avoid this problem with `vipw`. I don't know anymore if this is better fixed in vim or vipw... -- Mantas Mikulėnas -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
