Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use F_FULLFSYNC on OS X #13

Closed
untitaker opened this issue Jul 26, 2016 · 2 comments · Fixed by #50
Closed

Use F_FULLFSYNC on OS X #13

untitaker opened this issue Jul 26, 2016 · 2 comments · Fixed by #50
Labels
bug

Comments

@untitaker
Copy link
Owner

untitaker/python-atomicwrites#6
@untitaker untitaker added the bug label Aug 26, 2016
@untitaker
Copy link
Owner Author

dependent on nix-rust/nix#407

@probablykasper
Copy link

Judging by this issue, it seems like std::sync_all now uses F_FULLFSYNC, which I believe would fix this

@untitaker untitaker mentioned this issue Jan 11, 2022
Merged
@untitaker untitaker mentioned this issue Jan 11, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use std::fs::File::sync_all instead of nix::unistd::fsync. sunfishcode/rust-atomicwrites
2 participants
@untitaker @probablykasper