Enumeration
GLibFileSetContentsFlags
since: 2.66
Description
Flags to pass to g_file_set_contents_full() to affect its safety and performance.
Available since: 2.66
Members
-
G_FILE_SET_CONTENTS_NONE -
No guarantees about file consistency or durability. The most dangerous setting, which is slightly faster than other settings.
- Value:
0 - Available since: 2.66
- Value:
-
G_FILE_SET_CONTENTS_CONSISTENT -
Guarantee file consistency: after a crash, either the old version of the file or the new version of the file will be available, but not a mixture. On Unix systems this equates to an
fsync()on the file and use of an atomicrename()of the new version of the file over the old.- Value:
1 - Available since: 2.66
- Value:
-
G_FILE_SET_CONTENTS_DURABLE -
Guarantee file durability: after a crash, the new version of the file will be available. On Unix systems this equates to an
fsync()on the file (ifG_FILE_SET_CONTENTS_CONSISTENTis unset), or the effects ofG_FILE_SET_CONTENTS_CONSISTENTplus anfsync()on the directory containing the file after callingrename().- Value:
2 - Available since: 2.66
- Value:
-
G_FILE_SET_CONTENTS_ONLY_EXISTING -
Only apply consistency and durability guarantees if the file already exists. This may speed up file operations if the file doesn’t currently exist, but may result in a corrupted version of the new file if the system crashes while writing it.
- Value:
4 - Available since: 2.66
- Value: