Re: About close() in commit_lock_file()

On Tue, Aug 6, 2013 at 1:41 PM, Johannes Sixt wrote: > Am 8/5/2013 16:23, schrieb Duy Nguyen: >> close() is added in commit_lock_file(), before rename(), by 4723ee9 >> (Close files opened by lock_file() before unlinking. - 2007-11-13), >> which is needed by Windows. But doesn't that create a gap b

Re: About close() in commit_lock_file()

Am 8/5/2013 16:23, schrieb Duy Nguyen: > close() is added in commit_lock_file(), before rename(), by 4723ee9 > (Close files opened by lock_file() before unlinking. - 2007-11-13), > which is needed by Windows. But doesn't that create a gap between > close() and rename() on other platforms where anot

Re: About close() in commit_lock_file()

Duy Nguyen writes: > close() is added in commit_lock_file(), before rename(), by 4723ee9 > (Close files opened by lock_file() before unlinking. - 2007-11-13), > which is needed by Windows. But doesn't that create a gap between > close() and rename() on other platforms where another process can >

About close() in commit_lock_file()

close() is added in commit_lock_file(), before rename(), by 4723ee9 (Close files opened by lock_file() before unlinking. - 2007-11-13), which is needed by Windows. But doesn't that create a gap between close() and rename() on other platforms where another process can replace .lock file with somethi