Subj : Committing file changes
To   : Coridon Henshaw
From : mark lewis
Date : Sun Aug 13 2000 03:05 am

 CH> What's the proper way to 'checkpoint' an open file so as to
 CH> ensure that the file's control structures are consistant on
 CH> disk?  I would have thought that calling fflush() after every
 CH> file write would be sufficient,

is there a COMMIT instruction?

 CH> but a recent trap proved that
 CH> calling fflush() after file writes was no protection against
 CH> CHKDSK truncating the file well before the last write.  I
 CH> suppose I could close and reopen the file after every update,
 CH> but I was hoping to find a more elegant solution.  Any ideas?

sounds like it was caught up in the cache subsystem and not written to disk in 
time...

)\/(ark

 
* Origin: (1:3634/12)

.