Dealing with temporary files and permanent version storage

510 views
Skip to first unread message

John Grigutis

unread,
Feb 4, 2014, 2:46:33 PM2/4/14
to osxfus...@googlegroups.com
Hi all,

How does everyone deal with temporary files created as an application attempts to save changes? Here are some examples I've seen...

vi:
.filename.txt.swp

TextEdit:
.TemporaryItems/folders.1953456652
filename.rtf.sb-a52f1998-ucl2pZ/filename.rtf

Is there any way to prevent these files from being created? 

With TextEdit, I'm also running into messages that the document could not be saved and that the document is on a volume that does not support permanent version storage. My backend does support versions, but because of the way files are saved, they appear has completely new files (at least when it works).

Any advice would be appreciated.

Sam Moffatt

unread,
Feb 4, 2014, 5:58:28 PM2/4/14
to osxfus...@googlegroups.com
My suggestion is that you should handle all requests where reasonable irregardless of the "name" of the file. Doing "special" handling based on the filename in a way that breaks your file system contract will trigger inexplicable behaviour in applications.

As for the permanent version storage problem, I believe this is probably the closest explanation you'll get (e.g. it's not supported for non HFS+):


Cheers,

Sam

--
You received this message because you are subscribed to the Google Groups "OSXFUSE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to osxfuse-grou...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Ramesh D

unread,
May 18, 2015, 8:19:10 AM5/18/15
to osxfus...@googlegroups.com
Hi John,

r u fixed the temporary files problem actually i am also facing exactly same issue. 

Regards
Ramesh D

John Grigutis

unread,
May 20, 2015, 12:45:28 PM5/20/15
to osxfus...@googlegroups.com
No. I just let the Finder do as it pleases.

Sam Moffatt

unread,
May 20, 2015, 3:40:09 PM5/20/15
to osxfus...@googlegroups.com
Many apps use a strategy of writing a new file and then moving it to replace the original file. This is actually a good practice because it means that if the device runs out of space midway through your write, you don't corrupt the original file. If you try to do special handling on these files in such a way as to break the filesystem contract then you might find apps responding badly under normal operation.

Cheers,

Sam


--
Sam Moffatt

Note: I'm not at my desk, responses may be delayed. Apologies for the typos, smartphones aren't all that smart. 

--
You received this message because you are subscribed to the Google Groups "OSXFUSE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to osxfuse-grou...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages