delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2004/04/11/01:11:51

Message-Id: <200404110511.i3B5Bk5O015089@delorie.com>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "GARY VANSICKLE" <g DOT r DOT vansickle AT worldnet DOT att DOT net>
To: <cygwin AT cygwin DOT com>
Subject: RE: working sync() code
Date: Sun, 11 Apr 2004 00:11:26 -0500
MIME-Version: 1.0
In-Reply-To: <4078D165.3020303@att.net>
X-IsSubscribed: yes

[snip]
> 
> SUSv3 has this to say about sync():
> 
> <quote>
> The sync() function shall cause all information in memory that updates
> file
> systems to be scheduled for writing out to all file systems.
> 
> The writing, although scheduled, is not necessarily complete upon return
> from
> sync().
> </quote>
> 

"scheduled for writing out"?  Isn't that done at the time any
file/filesystem calls are made?  Unless I'm missing something, that quote
translates to, "sync() does nothing".


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019