RGBCube/Site
1
Fork 0
mirror of https://github.com/RGBCube/Site synced 2025-07-30 12:37:50 +00:00
Code Issues Activity Actions

dump(posix.fsync-pitfalls): update

Browse source
This commit is contained in:
RGBCube 2025-07-11 23:08:28 +03:00
parent 04f6b195f9
commit 51db068f5f
Signed by: RGBCube
SSH key fingerprint: SHA256:CzqbPcfwt+GxFYNnFVCqoN5Itn4YFrshg1TrnACpA5M
1 changed files with 0 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

4
site/dump/posix/fsync-pitfalls.md
View file

@ -41,8 +41,6 @@ This is a non-comprehensive list of the pitfalls of the `fsync` syscall.
I will expand this list as I have more questions about all the questionable I will expand this list as I have more questions about all the questionable
filesystems used and created by operating system enthusiasts. filesystems used and created by operating system enthusiasts.
---
## `fsync` does not ensure that a `fsync`'d file is visible in its parent directory ## `fsync` does not ensure that a `fsync`'d file is visible in its parent directory
From the manpage: From the manpage:
@ -56,8 +54,6 @@ This means that that you cannot rely on a file being in the directory after
Speaking about `fsync`ing a directory: Speaking about `fsync`ing a directory:
---
## `fsync` on a directory does not ensure children are `fsync`'d ## `fsync` on a directory does not ensure children are `fsync`'d
From the manpage: From the manpage: