User: Password:
|
|
Subscribe / Log in / New account

what's needed is a application barrier() call

what's needed is a application barrier() call

Posted Sep 9, 2009 19:06 UTC (Wed) by quotemstr (subscriber, #45331)
In reply to: what's needed is a application barrier() call by dlang
Parent article: POSIX v. reality: A position on O_PONIES

Ah, I see. fbarrier is an interest construct. You'd still need the rename trick in order to prevent observers from seeing inconsistent files at runtime. A program modifying /etc/passwd should prevent other applications from seeing an incompletely-written file. One could do this locks, but a simpler mechanism is rename.


(Log in to post comments)

what's needed is a application barrier() call

Posted Sep 9, 2009 20:55 UTC (Wed) by dlang (subscriber, #313) [Link]

correct, barrier() would not be a replacement for rename(), rename could (and probably should) imply a barrier.


Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds