Message 135917 - Python tracker

➜

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	milko.krachounov
Recipients	eric.araujo, eric.smith, exarkun, giampaolo.rodola, meatballhat, milko.krachounov, neologix, olemis, pitrou, tarek, vstinner
Date	2011-05-13.15:24:26
SpamBayes Score	2.3410221e-08
Marked as misclassified	No
Message-id	<1305300267.0.0.0166569082352.issue8604@psf.upfronthosting.co.za>
In-reply-to

Content
> Something's missing in all the implementations presented: > to make sure that the new version of the file is available afer > a crash, fsync must be called on the containing directory after > the rename. I upgraded my proposed approach to include dir fsync, and to do a copy when backing up instead of rename (is that good?) http://bazaar.launchpad.net/~exabyte/blackherd/async-refactor/view/66/blackherd/misc.py#L498

> Something's missing in all the implementations presented:
> to make sure that the new version of the file is available afer 
> a crash, fsync must be called on the containing directory after 
> the rename.

I upgraded my proposed approach to include dir fsync, and to do a copy when backing up instead of rename (is that good?)

http://bazaar.launchpad.net/~exabyte/blackherd/async-refactor/view/66/blackherd/misc.py#L498

History
Date	User	Action	Args
2011-05-13 15:24:27	milko.krachounov	set	recipients: + milko.krachounov, exarkun, pitrou, vstinner, eric.smith, giampaolo.rodola, tarek, eric.araujo, olemis, meatballhat, neologix
2011-05-13 15:24:26	milko.krachounov	set	messageid: <1305300267.0.0.0166569082352.issue8604@psf.upfronthosting.co.za>
2011-05-13 15:24:26	milko.krachounov	link	issue8604 messages
2011-05-13 15:24:26	milko.krachounov	create