On 26/10/2011 14:17, clayton wrote: > I have about 2G of files in my home directory, which I generally sync > multiple times per week. Scattered throughout this 2G, dated > throughout the life of this installation, are more then 40M of files named > *.unison.tmp-bad, ie. > > ../.miro/.unison.sqlitedb.f98298fee8e203a125e7b612dd798b92.unison.tmp-bad > ../.miro/.unison.sqlitedb.fcbc9c926749e3642f426dd093ae503c.unison.tmp-bad > ../.miro/.unison.miro-downloader-log.f98298fee8e203a125e7b612dd798b92.unison.tmp-bad > > etc. Unison does not seem to be cleaning up after itself, and worse, these > are hidden files that would fly under the radar and just > accumulate, apparently without limit.
In my experience, those happen when something goes wrong during synchronization. In the case of a file changed during synchronization (which seems to be the case here), the user is warned... but they can also appear when the connection is lost or when unison dies unexpectedly. I don't think Unison should delete these files itself (without a specific option, let's say), but maybe some warning when they are found could be useful. Cheers, -- Stéphane -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
