Issue #5092 has been reported by Daniel Pittman. ---------------------------------------- Feature #5092: ensure that files written to disk persist over machine crashes https://projects.puppetlabs.com/issues/5092
Author: Daniel Pittman Status: Unreviewed Priority: Normal Assignee: Category: file Target version: Affected Puppet version: development Keywords: Branch: At the moment puppet writes files in a wide range of ways, including some that are unsafe over a machine crash because they assume that 'rename' is atomic *and* durable, when it is only the former on many POSIX platforms. To achieve that puppet needs to ensure that the content of the replacement file is safely on disk before issuing the rename; any other mode of operation will result in a window (potentially minutes long) where some platforms will have neither the old or new versions of the file in place after an unclean restart of the filesystem. The puppet file type/provider is probably the most important target for fixing this, but it would be ideal to provide standard support for the 'atomic replace' operation across puppet - so that external users can also get this relatively tricky operation right. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
