Recovered Files folder in Trash

[Cuneyt]

FYI,

I noticed that the 3225137678 (folder) was in /private/var/tmp/folders.504/TemporaryItems/ after SuperDuper! copy.

[dnanian]

Yes, the eSellerate library is checking itself, and creates a temporary file there.

[Cuneyt]

... and eSellerate library is forgetting to delete them after checking, I suppose.

[dnanian]

That's right, although that doesn't really explain why it ends up in "Recovered Files".

[Cuneyt]

Originally Posted by dnanian

That's right, although that doesn't really explain why it ends up in "Recovered Files".

Once, I've written a script which was creating a temp file path to temporary items folder. I remember that if I don't delete that file at the end of the script, that file was in the Recovered Files folder on next startup. For this purpose I added a line that deletes the temp file at the end. Problem was gone. I suppose, it is something like that.

[dnanian]

That's weird. I wonder why they do that with /tmp... things create stuff in /tmp all the time without deleting them (although they should), but maybe they treat folders specially.

[Cuneyt]

You're right. While I was writing that script I was told that to create the temp file path to temporary items folder and it won't be needed to delete manually, OS X would delete it automatically on next startup. But, I noticed that it was not the case. May be something changed in OS X recently. Then I had to delete it at the end of the script. I suppose, OS X moves them into Recovered Files folder on startup if it find anything in the TemporaryItems folder considering as they were remained undeleted in the previous session. Just a thought.