On Jul 5, 2006, at 8:44 PM, Christopher Jett wrote:
RB2006r2 on OS 10.4.7
I have an application that takes a text file that is passed to it,
runs it through a unix command which generates a new text file (in the
TemporaryItemsFolder) with modified content. My application then adds
a resource fork to this new text file, and passes it to another
application which immediately picks it up from a watched folder. The
original file is deleted.
Whenever I reboot the machine, I am getting a TON of these new files
mentioned above in a Rescued Items folder in the Trash. This is even
though the files have long since done their function and been deleted
by the application they are handed to.
Any ideas as to why OS X keeps "rescuing" these files?
Good grief, I haven't seen this bug in about 5 years. It dates back to
the days of 9.0.x, where the Temporary Items folder would not be
emptied if the computer crashed; instead the "temporary" files would be
moved to a Rescued Items folder in the Trash. This resulted in a
progressive loss of disk space and was fixed in 9.1. However, it can
still happen in certain circumstances when running Classic in OS X.
Is your OS X application perhaps using a static path for Temporary
Items - such as Volume(0).Child("Temporary Items")? Alternatively, are
you booting OS 9 on this machine?
Eric M. Williams
Oxalyn Software
http://software.oxalyn.com/
AE Monitor
http://software.oxalyn.com/AEMonitor/
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
