luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-02-04 18:26:19 +01:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'non-atomicity-of-g_file_set_contents' into 'master'

Browse Source 
gfileutils: document non-atomicity of g_file_set_contents()

See merge request GNOME/glib!118
This commit is contained in:
Philip Withnall 2018-06-19 11:13:50 +00:00
commit dd51b05e19
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
glib/gfileutils.c
View File

@ -1173,6 +1173,17 @@ write_to_temp_file (const gchar *contents,
* lists, metadata etc. may be lost. If @filename is a symbolic link, * lists, metadata etc. may be lost. If @filename is a symbolic link,
* the link itself will be replaced, not the linked file. * the link itself will be replaced, not the linked file.
* *
* - On UNIX, if @filename already exists and is non-empty, and if the system
* supports it (via a journalling filesystem or equivalent), the fsync()
* call (or equivalent) will be used to ensure atomic replacement: @filename
* will contain either its old contents or @contents, even in the face of
* system power loss, the disk being unsafely removed, etc.
*
* - On UNIX, if @filename does not already exist or is empty, there is a
* possibility that system power loss etc. after calling this function will
* leave @filename empty or full of NUL bytes, depending on the underlying
* filesystem.
*
* - On Windows renaming a file will not remove an existing file with the * - On Windows renaming a file will not remove an existing file with the
* new name, so on Windows there is a race condition between the existing * new name, so on Windows there is a race condition between the existing
* file being removed and the temporary file being renamed. * file being removed and the temporary file being renamed.