🚀 go-pugleaf

In article <CHUCK.PHILLIPS.90Aug9130916@halley.FtCollins.NCR.COM> Chuck.Phillips@FtCollins.NCR.COM (Chuck.Phillips) writes:
>Question for the OS/disk experts: Is it possible for an AmigaOS program to
>open a file for writing and then exit _normally_ (no guru or power failure)
>without closing the file, possibly creating a validation error?  (Exclude
>programs directly accessing the disk device)

>>>>> On 10 Aug 90 21:14:54 GMT, jesup@cbmvax.commodore.com (Randell Jesup) said:
Randell> Sure, those could certainly cause validation to be needed (but no
Randell> problems are likely to result in most cases).

>Question for C=: If this is possible, are there plans to correct this in a
>future release?

Randell> It would be hard, since we don't know why the file was left open,
Randell> even if we tracked what files a process opens.  Maybe the FH was
Randell> passed to another process.

Thanks for the response.  Another question:

Is it possible to write a program that will simply close every open file on
a device? (Possibly prompting the user interactively) DiskDoctor seems like
extreme overkill to handle these cases; it also has the effect of
undeleting lots of files I really don't want to have to clean up again.

If someone could mail or post a program (or C fragment) that does this, it
would be greatly appreciated.  No fancy interface required.

	Thanks in advance,
--
Chuck Phillips  MS440
NCR Microelectronics 			Chuck.Phillips%FtCollins.NCR.com
2001 Danfield Ct.
Ft. Collins, CO.  80525   		uunet!ncrlnk!ncr-mpd!bach!chuckp