TSVNCache is creating "etc" folders everywhere

[Benoit Fouletier]

So I have a bit of a weird issue, I see "etc" folders being created more or less randomly anywhere on my drives, like I have an explorer window open at some path for hours, and suddenly poof the folder appears.

According to ProcessMonitor, this is caused by TSVNCache.exe... any idea why, and what I can do to stop it?

Here's an example (not that it doesn't just happen in this folder, can be pretty much any folder):

[Stefan]

If you look at the output from ProcMon you can see that the TSVNCache.exe process does not create those folders but only queries them when they're there.

So you have to find the process that creates them, not queries them.

Stefan

[Benoit Fouletier]

Well, the timings are suspicious though aren't they? TSVNCache.exe is the very first one to query that path, then right after explorer.exe does the creation.

Since Tortoise is hooked into the explorer, I figured it might be creating the actual file on its behalf? Could be wrong though, I have no idea how such hooks work :) !

[Stefan]

On Friday, November 17, 2017 at 3:41:45 PM UTC+1, Benoit Fouletier wrote:

Well, the timings are suspicious though aren't they? TSVNCache.exe is the very first one to query that path, then right after explorer.exe does the creation.

Since Tortoise is hooked into the explorer, I figured it might be creating the actual file on its behalf? Could be wrong though, I have no idea how such hooks work :) !

explorer does not create the folder either. Yes, it's a CreateFile call, but only with read attributes and with "list" access, i.e. explorer tries to list the files inside it.

And the TSVNCache process monitors the file system for changes, and if it detects a change it determines whether it should query those changes to update the overlays.

Also: the folder was created at 14:31:23, but the cache process accesses it at 14:32:48, so there's quite some time between the creation and when the cache queries it.

Stefan

[Benoit Fouletier]

Hmm, I see, indeed I read it wrong.

Any idea why the event that actually created the file show up in the monitor? maybe I messed up the filter... I filtered by path = "D:\Unity-source\etc".

Le vendredi 17 novembre 2017 16:01:42 UTC+1, Stefan a écrit :

[Stefan]

On Friday, November 17, 2017 at 4:07:00 PM UTC+1, Benoit Fouletier wrote:

Hmm, I see, indeed I read it wrong.

Any idea why the event that actually created the file show up in the monitor? maybe I messed up the filter... I filtered by path = "D:\Unity-source\etc".

Well, if the folder is not real but a junction/hardlink then it won't show up in the path.

Why don't you filter for "contains" and just "\etc" - that should catch everything.

Stefan