Date: Thu, 8 Apr 1999 11:34:32 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Alain Magloire <alainm AT rcsm DOT ece DOT mcgill DOT ca>
cc: djgpp-workers AT delorie DOT com
Subject: Re: v2.03 release: what else has to be done?
In-Reply-To: <199904062151.RAA16071@spock2.ECE.McGill.CA>
Message-ID: <Pine.SUN.3.91.990408113415.29868S-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 6 Apr 1999, Alain Magloire wrote:

> My Posix 1003.1, 1996  p 214(8.2.3.4) lines 363-367 says:
> fflush:
> 	The ffush() functions shall mark for update the st_ctime and st_mtime
> 	fields of the underlying file if the stream was writable and if
> 	buffered data had not been written to the file yet.
> 	The underlying functions are write() and lseek().

I'm actually interested in this part, because it seems to be relevant
for the fflush/fsync problem in another thread.  This excerpt seems
like it requires fflush to also synchronize the filesystem, at least
to some extent, which might suggest we *do* need to call fsync from
inside fflush.

However, the exact interpretation of ``shall mark for update'' is not
clear to me.  AFAIK, in Unix, this means that the system will not
actually update the data untill something happens.  What is the event
that would trigger this update in this case?