> How is the way your C code works better than first linking src to tmp
> and then, assuming that succeeds, doing the various necessary checks and
> either renaming it to dst or deleting it depending on the outcome?
Link is synchronous on traditional Unix filesystems and on NFS.
> Isn't the !S_ISREG(srcstat.st_mode) check [...] unsafe not only if
> the file is modified in place, but also if it is removed and another
> created which uses the same inode?
This code assumes that i-nodes are not changed in place, and that inum
wraparound doesn't happen. There's not much more you can do efficiently.
And now could you /please/ answer the numbered points in message
<[EMAIL PROTECTED]> dated 29 August?
Juliusz
_______________________________________________
darcs-devel mailing list
[email protected]
http://www.abridgegame.org/cgi-bin/mailman/listinfo/darcs-devel
