🚀 go-pugleaf

In article <9032@cbmvax.commodore.com> mks@cbmvax.commodore.com (Michael Sinz - CATS) writes:
>In article <1336@becker.UUCP> douglee@becker.UUCP (Doug Lee) writes:
>>
>> quick question for AmigaDOS gurus. While capturing to ram: with my terminal
>> , I can do a list at any time and get the current size of the file I'm writing
>> to. When capturing to rad: I get 'empty' for filesize until I close it. Why
>> do these two devices behave so differently when there is a write lock?
>>				    <<<Doug>>>

>                                                  For this
>reason, filing systems normally only update such information on close
>of the file or on certain flush situations.
>
>|      /// Michael Sinz -- CATS/Amiga Software Engineer                |
>|     ///  PHONE 215-431-9422  UUCP ( uunet | rutgers ) !cbmvax!mks    |
One reason that you might want the other behavior (update directory a lot)
is so that in case of a guru you can still get back part of the file,
and maybe even restart the transfer.

How can one force a flush of a file opened in the various ways
(5 of them: Open, manx open/fopen, lattice open/fopen)?
Does doing this flush operation guarantee that the write has occured,
or is there an equivilent to the unix sync() that one can call?
This seems like a desirable option for file-transfer programs, and for
programs that write a debugging logfile (so you can see where they died).
--------------------------------------------------------------------
Steve Tell					tell@wsmail.cs.unc.edu
CS Grad Student, UNC Chapel Hill.