Hi
Already posted about ghost items here : ghost folders in shares
But this seems not to be enough.
I create a share and synchronize it with several devices. At some point, I realize that the trash on a linux server, which is represented by .TrashXXXX files, has been duplicated.
And that’s when the trouble began: yes, I read the damn doc, and saw that there’s exclusion management with the .stignore file. But that’s the technical side of things. What’s missing are really concrete user cases: you’ve created a share, and duplicated it on several devices, and you see files you don’t want to share, except that you don’t necessarily know where they’ve gone.
What’s more, even if you do know (in my example, if you have a single Linux machine, which .stignore file should you enter with the exclusion? that of the server that (might) send the file, or that of all the destinations?
And frankly, I’m sure I’m not the only one with .TrashXXX files, desktop.ini files, and other ff_sync.db files (those created by Foldersync, or freefilesync, or others) that you don’t want to see spread everywhere: how do you deal with that before it’s too late?
And for me now, how do I go about it when it’s too late? : I’ve just added an android machine to an existing share by declaring this machine only on my NAS ( “receive only” as a first step on that new machine) : this new machine tells me “there are 13 files not sync, and purple box empty…”.
So, on the NAS and for this share, I empty the .stignore that contained “.Trash*” + “.Trash**”, and then, the NAS outputs “out of sync”, 13 items, and in detail “syncing: no connected device has the required version of this file” on a .TrashXXXX file that no longer exists anywhere ( because I removed them of course!)
and I don’t even want to talk about these files which were present on my android devices, except that they were not found in the local file manager when I tried to delete them…(mounted sdcard on laptop : no such files… really stranges ghost files… As if syncthing could persuade the local system of the presence of non-existent files…