search for: movefileexw

...ace by first writing a buffer to a temp file and then renaming that temp file to become the final file in the cache. After r315079, when 'rename' became more POSIX-compliant, this scheme guarantees atomicity of writing a file to the cache, (except on Wine, where (in some cases) non-atomic ::MoveFileExW is used). However, 'rename' might fail and return an error code in several different situations. If this happens, we will fall back to a direct write to the file, which is neither atomic, nor avoids race conditions (causing problem #3). An example where 'rename' can fail on both Wi...

...writing a buffer to a temp file and then > renaming that temp file to become the final file in the cache. After > r315079, when ‘rename’ became more POSIX-compliant, this scheme guarantees > atomicity of writing a file to the cache, > (except on Wine, where (in some cases) non-atomic ::MoveFileExW is used). > > However, ‘rename’ might fail and return an error code in several different > situations. If this happens, we will fall back to a direct write to the > file, which is neither atomic, nor avoids race conditions (causing problem > #3). > An example where 'rename'...

...a race by first writing a buffer to a temp file and then renaming that temp file to become the final file in the cache. After r315079, when ‘rename’ became more POSIX-compliant, this scheme guarantees atomicity of writing a file to the cache, > (except on Wine, where (in some cases) non-atomic ::MoveFileExW is used). > > However, ‘rename’ might fail and return an error code in several different situations. If this happens, we will fall back to a direct write to the file, which is neither atomic, nor avoids race conditions (causing problem #3). > An example where 'rename' can fail on...

...ce by first writing a buffer to a temp file and then renaming that temp file to become the final file in the cache. After r315079, when ‘rename’ became more POSIX-compliant, this scheme guarantees atomicity of writing a file to the cache, >> (except on Wine, where (in some cases) non-atomic ::MoveFileExW is used). >> >> However, ‘rename’ might fail and return an error code in several different situations. If this happens, we will fall back to a direct write to the file, which is neither atomic, nor avoids race conditions (causing problem #3). >> An example where 'rename'...

...a data race by first writing a buffer to a temp file and then renaming that temp file to become the final file in the cache. After r315079, when ‘rename’ became more POSIX-compliant, this scheme guarantees atomicity of writing a file to the cache, (except on Wine, where (in some cases) non-atomic ::MoveFileExW is used). However, ‘rename’ might fail and return an error code in several different situations. If this happens, we will fall back to a direct write to the file, which is neither atomic, nor avoids race conditions (causing problem #3). An example where 'rename' can fail on both Windows an...

...a data race by first writing a buffer to a temp file and then renaming that temp file to become the final file in the cache. After r315079, when ‘rename’ became more POSIX-compliant, this scheme guarantees atomicity of writing a file to the cache, (except on Wine, where (in some cases) non-atomic ::MoveFileExW is used). However, ‘rename’ might fail and return an error code in several different situations. If this happens, we will fall back to a direct write to the file, which is neither atomic, nor avoids race conditions (causing problem #3). An example where 'rename' can fail on both Windows an...

...ing a buffer to a temp file and then > renaming that temp file to become the final file in the cache. After > r315079, when ‘rename’ became more POSIX-compliant, this scheme guarantees > atomicity of writing a file to the cache, > > (except on Wine, where (in some cases) non-atomic ::MoveFileExW is used). > > > > However, ‘rename’ might fail and return an error code in several different > situations. If this happens, we will fall back to a direct write to the > file, which is neither atomic, nor avoids race conditions (causing problem > #3). > > An example where...

...a data race by first writing a buffer to a temp file and then renaming that temp file to become the final file in the cache. After r315079, when ‘rename’ became more POSIX-compliant, this scheme guarantees atomicity of writing a file to the cache, (except on Wine, where (in some cases) non-atomic ::MoveFileExW is used). However, ‘rename’ might fail and return an error code in several different situations. If this happens, we will fall back to a direct write to the file, which is neither atomic, nor avoids race conditions (causing problem #3). An example where 'rename' can fail on both Windows an...

...a race by first writing a buffer to a temp file and then renaming that temp file to become the final file in the cache. After r315079, when ‘rename’ became more POSIX-compliant, this scheme guarantees atomicity of writing a file to the cache, > (except on Wine, where (in some cases) non-atomic ::MoveFileExW is used). > > However, ‘rename’ might fail and return an error code in several different situations. If this happens, we will fall back to a direct write to the file, which is neither atomic, nor avoids race conditions (causing problem #3). > An example where 'rename' can fail on...

...ing a buffer to a temp file and then > renaming that temp file to become the final file in the cache. After > r315079, when ‘rename’ became more POSIX-compliant, this scheme guarantees > atomicity of writing a file to the cache, > > (except on Wine, where (in some cases) non-atomic ::MoveFileExW is used). > > > > However, ‘rename’ might fail and return an error code in several different > situations. If this happens, we will fall back to a direct write to the > file, which is neither atomic, nor avoids race conditions (causing problem > #3). > > An example where...

...a data race by first writing a buffer to a temp file and then renaming that temp file to become the final file in the cache. After r315079, when ‘rename’ became more POSIX-compliant, this scheme guarantees atomicity of writing a file to the cache, (except on Wine, where (in some cases) non-atomic ::MoveFileExW is used). However, ‘rename’ might fail and return an error code in several different situations. If this happens, we will fall back to a direct write to the file, which is neither atomic, nor avoids race conditions (causing problem #3). An example where 'rename' can fail on both Windows an...