➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ronaldoussoren
Recipients nadeem.vawda, neologix, ronaldoussoren, sdaoden, vstinner
Date 2011-04-20.12:16:38
SpamBayes Score 3.6801557e-06
Marked as misclassified No
Message-id <1303301799.41.0.773549718516.issue11877@psf.upfronthosting.co.za>
In-reply-to
Content 
See <http://www.kernel.org/doc/man-pages/online/pages/man2/fsync.2.html> for linux' behavior, in particular: linux doesn't guarantee that data gets writting to the disk when you call fsync, only that the data gets pushed to the storage device.

This is the same behavior as fsync on OSX, and OSX also has a second API that provides stronger guarantees. 

With your patch it is no longer possible to call the C function fsync on OSX, even though it is good enough for a lot of use cases. As os.fcntl already supports F_FULLSYNC I see no good reason to change the implementation of os.fsync on OSX.

BTW. The need to use F_FULLSYNC in issue 11277 might be a bug in OSX itself, have you filed an issue in Apple's tracker?
History
Date User Action Args
2011-04-20 12:16:39ronaldoussorensetrecipients: + ronaldoussoren, vstinner, nadeem.vawda, neologix, sdaoden
2011-04-20 12:16:39ronaldoussorensetmessageid: <1303301799.41.0.773549718516.issue11877@psf.upfronthosting.co.za>
2011-04-20 12:16:38ronaldoussorenlinkissue11877 messages
2011-04-20 12:16:38ronaldoussorencreate