search for: movefileex

...en though + * http://msdn.microsoft.com/en-us/library/windows/desktop/ms724884.aspx + * and + * http://blogs.msdn.com/oldnewthing/archive/2009/10/08/9904646.aspx + * claim that it is not possible to store empty strings in MULTI_SZ + * string lists, such lists are used by Windows itself: + * + * The MoveFileEx function can schedule files to be renamed (or + * removed) at restart time by storing pairs of filenames in the + * HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations + * value. + * + * The documentation for MoveFileEx + * (http://msdn.microsoft.com/en-us/library/wind...

> -----Original Message----- > From: Uwe Ligges [SMTP:ligges@statistik.uni-dortmund.de] > Sent: Thursday, August 12, 2004 5:38 PM > To: Walke, Rainer > Cc: R-devel > Subject: Re: [Rd] (PR#7163) Install packages does not work on Win2003 > server > > Walke, Rainer wrote: > > > >a) It works for me. > > >b) If it works for you on some Windows

...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 W...

...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 o...

...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 a...

...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 a...

...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 a...

...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 o...

...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...

...ntLog (0xcafe4242) stub eventlog.c:863: Tests skipped: No events were written to the eventlog eventlog.c:1086: Test failed: Expected an eventlog file eventlog.c:1113: Test succeeded inside todo block: Could not delete the registry tree : 0 eventlog.c:1120: Test succeeded inside todo block: Expected MoveFileEx to succeed: 1 make[2]: *** [eventlog.ok] Error 24 make[2]: Leaving directory `/hide/trip/build/wine-1.3.26/dlls/advapi32/tests' make[1]: *** [dlls/advapi32/tests/__test__] Error 2 make[1]: Leaving directory `/hide/trip/build/wine-1.3.26' dh_auto_test: make -j1 test returned exit code 2 make...

...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 a...

...target directory exists, when not broken to do the move at all. Still, according to POSIX, mv/renameat should work in this context with the target being an empty directory, it works on my systems and that it does not on some is probably a bug. Likewise, from my reading of the documentation of MoveFileEx, the file rename should also work on Windows with the empty target directory with the flags we use (and it is also implied in CERT advisory FIO10-C), but contradicts what I am seeing on my system. This is why I had added the deletion on Windows before. Pragmatically, there is probably no point...

On Tue, May 7, 2019 at 9:05 AM Tomas Kalibera <tomas.kalibera at gmail.com> wrote: > > Thanks for the report. According to my reading, this use of "mv" is ok > and the renameat2() call which the invocation of "mv" leads to is also > ok and allowed by POSIX in this context. It could only fail with EEXIST > if the target directory (path/pkg) was not empty.

...e_assignment(). d3dcompiler/tests: Add more tests for swizzles. d3dcompiler: Unwrap swizzles from the left-hand side of an assignment. d3dcompiler: Separate out an hlsl_deref structure and store it in hlsl_ir_assignment directly. kernel32: Reimplement ReplaceFile() on top of MoveFileEx(). quartz/tests: Add a test for aggregation on the seeking passthrough object. strmbase: Standardize aggregation of the seeking passthrough object. strmbase: Separate the seeking passthrough object from its implementation. strmbase: Get rid of the PassThruImpl typedef....

...2: Test processing of expose events. Dan Hipschman (14): qmgr: Add critical sections for jobs and files. qmgr: Add infrastructure for background file transferring. qmgr: Implement local file background "downloads." kernel32: Add the MOVEFILE_WRITE_THROUGH flag for MoveFileEx (stub). qmgr: Implement BackgroundCopyJob_Complete. qmgr: Transfer files given by URL (including HTTP, etc). qmgr: Transfer files given by URL (including HTTP, etc). qmgr: Implement progress updates for downloads given by URL. qmgr: Implement IBackgroundCopyJob_AddFile...