rfc:fsync_function
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionNext revisionBoth sides next revision | ||
rfc:fsync_function [2021/01/30 00:37] – created dwgebler | rfc:fsync_function [2021/02/01 17:31] – add fdatasync to proposal dwgebler | ||
---|---|---|---|
Line 3: | Line 3: | ||
* Date: 2021-01-30 | * Date: 2021-01-30 | ||
* Author: David Gebler, davidgebler@gmail.com | * Author: David Gebler, davidgebler@gmail.com | ||
- | * Status: | + | * Status: |
* First Published at: http:// | * First Published at: http:// | ||
Line 11: | Line 11: | ||
===== Proposal ===== | ===== Proposal ===== | ||
This RFC would add an fsync() function accepting a single parameter of a stream resource. The implementation of this function would be a thin wrapper around the standard C fsync (or equivalent _commit on Windows API, which uses an identical signature). | This RFC would add an fsync() function accepting a single parameter of a stream resource. The implementation of this function would be a thin wrapper around the standard C fsync (or equivalent _commit on Windows API, which uses an identical signature). | ||
+ | |||
+ | The related function fdatasync() which syncs data but not necessarily metadata would also be added, however this is not supported on Windows and the proposal there is to still provide fdatasync() but merely as an alias of fsync(). On POSIX, fdatasync() is properly implemented. | ||
<code php> | <code php> | ||
Line 18: | Line 20: | ||
bool(true) | bool(true) | ||
+ | |||
+ | $fp = fopen(' | ||
+ | fwrite($fp," | ||
+ | var_dump(fsync($fp)); | ||
+ | |||
+ | Warning: fsync(): Can't fsync this stream in php shell code on line 1 | ||
+ | bool(false) | ||
+ | |||
+ | $fp = fopen(' | ||
+ | // Can't fsync / fdatasync read-only file, but it is a valid file handle, so we just return false with no warning. | ||
+ | var_dump(fsync($fp)); | ||
+ | bool(false) | ||
</ | </ | ||
rfc/fsync_function.txt · Last modified: 2021/04/13 14:10 by nikic