Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!gatech!hope
From: hope@gatech.UUCP
Newsgroups: comp.unix.wizards,comp.unix.questions,comp.sys.att
Subject: O_SYNC and filesystem updating
Message-ID: <11470@gatech.EDU>
Date: Fri, 6-Feb-87 09:10:59 EST
Article-I.D.: gatech.11470
Posted: Fri Feb  6 09:10:59 1987
Date-Received: Sat, 7-Feb-87 19:29:29 EST
Organization: School of Information and Computer Science, Georgia Tech, Atlanta
Lines: 20
Keywords: O_SYNC, System V, reliability? What reliability?
Xref: watmath comp.unix.wizards:856 comp.unix.questions:937 comp.sys.att:155

I realize that this subject may have already been beaten to death, but:

When a (regular) file is opened with the O_SYNC flag, the write
syscalls "will not return until both the file data and file status
have been physically updated." (System V 'write' man page)

By "file status" are we to assume that the write syscall also waits for
the superblock to be updated due to inode information changing?  Also, does
it wait for the update of the directory where the file resides (e.g. in
the event of file creation)?

I don't really have the time to look through the source code, and would
appreciate any insight or knowledge on the subject.

Thanks.
-- 
Theodore Hope
School of Information & Computer Science, Georgia Tech, Atlanta GA 30332
CSNet:	Hope @ gatech		ARPA:	Hope@ics.GATECH.EDU
uucp:	...!{akgua,decvax,hplabs,ihnp4,linus,seismo,ulysses}!gatech!hope