Displaying 12 results from an estimated 12 matches for "movefile_copy_allowed".
2018 Mar 22
4
[pre-RFC] Data races in concurrent ThinLTO processes
...have two different functions, one POSIX-compliant, not allowing renames across different volumes, another non-POSIX-compliant.
Before r315079, the function 'rename', (in the case when the destination file isn't opened), boiled down to calling the function 'MoveFileExW' with the MOVEFILE_COPY_ALLOWED flag set, allowing renaming files across the volumes.
The current implementation of the function 'rename' (in 'rename_internal'), essentially calls 'SetFileInformationByHandle'. This function is fast and atomic, so in a sense, it's an improvement over the previously used...
2011 Mar 02
1
file.rename(): Guaranteed to be complete or not at all?
Hi,
assume I have an existing file 'pathname' and I want to rename it to
'pathnameN' (which does not exist). I use:
res <- file.rename(pathname, pathnameN);
Is it guaranteed that:
(1) if res == TRUE, the file now have name 'pathnameN' and there is no
file with name 'pathname'?
(2) if res == FALSE, nothing has changed?
or could it theoretically also be the
2018 Mar 27
2
[pre-RFC] Data races in concurrent ThinLTO processes
...ions, one POSIX-compliant, not
> allowing renames across different volumes, another non-POSIX-compliant.
>
> Before r315079, the function 'rename', (in the case when the destination
> file isn't opened), boiled down to calling the function 'MoveFileExW' with
> the MOVEFILE_COPY_ALLOWED flag set, allowing renaming files across the
> volumes.
> The current implementation of the function ‘rename’ (in
> 'rename_internal'), essentially calls 'SetFileInformationByHandle'. This
> function is fast and atomic, so in a sense, it's an improvement over the
>...
2018 Mar 22
0
[pre-RFC] Data races in concurrent ThinLTO processes
...fferent functions, one POSIX-compliant, not allowing renames across different volumes, another non-POSIX-compliant.
>
> Before r315079, the function 'rename', (in the case when the destination file isn't opened), boiled down to calling the function 'MoveFileExW' with the MOVEFILE_COPY_ALLOWED flag set, allowing renaming files across the volumes.
> The current implementation of the function ‘rename’ (in 'rename_internal'), essentially calls 'SetFileInformationByHandle'. This function is fast and atomic, so in a sense, it's an improvement over the previously used ...
2018 Mar 27
0
[pre-RFC] Data races in concurrent ThinLTO processes
...functions, one POSIX-compliant, not allowing renames across different volumes, another non-POSIX-compliant.
>>
>> Before r315079, the function 'rename', (in the case when the destination file isn't opened), boiled down to calling the function 'MoveFileExW' with the MOVEFILE_COPY_ALLOWED flag set, allowing renaming files across the volumes.
>> The current implementation of the function ‘rename’ (in 'rename_internal'), essentially calls 'SetFileInformationByHandle'. This function is fast and atomic, so in a sense, it's an improvement over the previously use...
2018 Mar 27
1
[pre-RFC] Data races in concurrent ThinLTO processes
...have two different functions, one POSIX-compliant, not allowing renames across different volumes, another non-POSIX-compliant.
Before r315079, the function 'rename', (in the case when the destination file isn't opened), boiled down to calling the function 'MoveFileExW' with the MOVEFILE_COPY_ALLOWED flag set, allowing renaming files across the volumes.
The current implementation of the function ‘rename’ (in 'rename_internal'), essentially calls 'SetFileInformationByHandle'. This function is fast and atomic, so in a sense, it's an improvement over the previously used 'Mo...
2018 Mar 27
4
[pre-RFC] Data races in concurrent ThinLTO processes
...have two different functions, one POSIX-compliant, not allowing renames across different volumes, another non-POSIX-compliant.
Before r315079, the function 'rename', (in the case when the destination file isn't opened), boiled down to calling the function 'MoveFileExW' with the MOVEFILE_COPY_ALLOWED flag set, allowing renaming files across the volumes.
The current implementation of the function ‘rename’ (in 'rename_internal'), essentially calls 'SetFileInformationByHandle'. This function is fast and atomic, so in a sense, it's an improvement over the previously used 'Mo...
2018 Mar 27
0
[pre-RFC] Data races in concurrent ThinLTO processes
...POSIX-compliant, not
> allowing renames across different volumes, another non-POSIX-compliant.
>
>
>
> Before r315079, the function 'rename', (in the case when the destination
> file isn't opened), boiled down to calling the function 'MoveFileExW' with
> the MOVEFILE_COPY_ALLOWED flag set, allowing renaming files across the
> volumes.
>
> The current implementation of the function ‘rename’ (in
> 'rename_internal'), essentially calls 'SetFileInformationByHandle'. This
> function is fast and atomic, so in a sense, it's an improvement over th...
2018 Mar 27
2
[pre-RFC] Data races in concurrent ThinLTO processes
...have two different functions, one POSIX-compliant, not allowing renames across different volumes, another non-POSIX-compliant.
Before r315079, the function 'rename', (in the case when the destination file isn't opened), boiled down to calling the function 'MoveFileExW' with the MOVEFILE_COPY_ALLOWED flag set, allowing renaming files across the volumes.
The current implementation of the function ‘rename’ (in 'rename_internal'), essentially calls 'SetFileInformationByHandle'. This function is fast and atomic, so in a sense, it's an improvement over the previously used 'Mo...
2018 Mar 27
0
[pre-RFC] Data races in concurrent ThinLTO processes
...fferent functions, one POSIX-compliant, not allowing renames across different volumes, another non-POSIX-compliant.
>
> Before r315079, the function 'rename', (in the case when the destination file isn't opened), boiled down to calling the function 'MoveFileExW' with the MOVEFILE_COPY_ALLOWED flag set, allowing renaming files across the volumes.
> The current implementation of the function ‘rename’ (in 'rename_internal'), essentially calls 'SetFileInformationByHandle'. This function is fast and atomic, so in a sense, it's an improvement over the previously used ...
2018 Mar 27
0
[pre-RFC] Data races in concurrent ThinLTO processes
...POSIX-compliant, not
> allowing renames across different volumes, another non-POSIX-compliant.
>
>
>
> Before r315079, the function 'rename', (in the case when the destination
> file isn't opened), boiled down to calling the function 'MoveFileExW' with
> the MOVEFILE_COPY_ALLOWED flag set, allowing renaming files across the
> volumes.
>
> The current implementation of the function ‘rename’ (in
> 'rename_internal'), essentially calls 'SetFileInformationByHandle'. This
> function is fast and atomic, so in a sense, it's an improvement over th...
2018 Mar 27
1
[pre-RFC] Data races in concurrent ThinLTO processes
...have two different functions, one POSIX-compliant, not allowing renames across different volumes, another non-POSIX-compliant.
Before r315079, the function 'rename', (in the case when the destination file isn't opened), boiled down to calling the function 'MoveFileExW' with the MOVEFILE_COPY_ALLOWED flag set, allowing renaming files across the volumes.
The current implementation of the function ‘rename’ (in 'rename_internal'), essentially calls 'SetFileInformationByHandle'. This function is fast and atomic, so in a sense, it's an improvement over the previously used 'Mo...