[Rpm-maint] [rpm-software-management/rpm] Add macro to force fsync() on close() (#187)

[Jeff Johnson]

@pmatila: if you *do* attempt to configure +/- fsync(2) somehow, then durability is likely the better approach. By "durability", I mean "this file is essential to booting" (and hence is worth paying the cost of fsync(2) to ensure that the file is correctly written to disk).

Some simple patterns could be applied to paths to choose fsync(2) (or not). One could also add a %sync flag in spec files to set a flag for per-file-durability under packager control.

OTOH, per-file != per-package or per-transaction durability. But at least per-package atomicity can be achieved by delaying the FILE.TID -> FILE rename into place. Unclear whether its worth the effort *shrug*.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/187#issuecomment-294410365
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20170416/4785f208/attachment.html>