Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!cbosgd!gatech!gerardo
From: gerardo@gatech.EDU (Gerardo Brenes)
Newsgroups: comp.unix.questions,comp.unix.wizards,comp.databases
Subject: O_SYNC option in SVR3 open system call
Message-ID: <5922@gatech.EDU>
Date: Sat, 8-Nov-86 22:46:55 EST
Article-I.D.: gatech.5922
Posted: Sat Nov  8 22:46:55 1986
Date-Received: Sun, 9-Nov-86 06:34:22 EST
Organization: School of Information and Computer Science, Georgia Tech, Atlanta
Lines: 29
Keywords: waiting for physical update?
Xref: watmath comp.unix.questions:7 comp.unix.wizards:4 comp.databases:2


Subject: SVR3 open with O_SYNC option
Newsgroups: comp.unix.questions
Keywords: really waits for physical update?

In the reference manual for SVR3 for the ATT 3B2 machine, the description for
the open system call mentions an option O_SYNC. It literally says:

	O_SYNC	When opening a regular file, this flag affects subsequent
		writes. If set, each write (2) will wait for both the file
		data and file status to be physically updated.

Does anybody out there knows if this wait is for real or is the same BSD idea
of the "fflush" in which blocks are merely "scheduled" and the call returns as 
if they were actually written to the device. 

Please use e-mail to answer and I'll post a summary of comments if enough
interest is shown.  Thanks a lot for your help.

Gerardo Brenes

================================================================================
Smile ! They might think you are nuts and just go along with it!
================================================================================
School of Information & Computer Science, Georgia Tech, Atlanta GA 30332
CSNet:  gerardo@GATech	
ARPA:	gerardo%GATech.CSNet@CSNet-Relay.ARPA
uucp:	...!{akgua,allegra,hplabs,ihnp4,linus,seismo,ulysses}!gatech!gerardo
================================================================================