Christian_K
-
Posts
4 -
Joined
-
Last visited
Posts posted by Christian_K
-
-
as vadim has said :
AppDataAppData\*Your OS is Windows and you should use "\" in the path.That's working for me, I have windows machines on both sides of the sync... what if one side of the sync is Win and the other side is a Linux machine ? Should the paths in .syncignore be different ?Not working for me. Do you have a unidirectional sync also, i.e. are you using the read-only key?
-
... well, as I said it is completely ignored
Remember that any changes you make to .SyncIgnore won't take affect until you restart Sync, and that your .SyncIgnore files need to be identical for the folder you're syncing on all your devices
yes, I did a restart that as I said. The settings are .SyncIgnore is still completely ignored. Thanks for your response anyway.
-
Actually I have exactly the same issue described in this thread and in other threads.
In my environment all settings in .SyncIgnore are completely ignored.
I did various tests with a sample folder with different .SyncIgnore entries:
- path separators / and \
- with and without * and \* at the line end.
- with Bittorrent Sync restart
- without having the .SyncIgnore file opened in my editor
No solution yet.
I am doing Windows 7 Ultimate 64 bit --> read-only sync --> Linux (Synology NAS).
Might be a problem of the unidirectional sync (read-only sync).
Looking forward for a solution.
Thx in advance.
.syncignore issue with subfolders of windows user profile
in Sync General Discussion
Posted
Well I gave it another try.
I was able to run tests doing a unidirectional sync from Windows 7 64bit > Mac
(I don't see any version information but BTSync has been downloaded today.)
1.) Excluding folders
Good news: I was able to fully exclude a folder:
... fully excluded the folder named 'a' of my sync root directory.
Fully exclude means that the folder does not even appear on sync target. If you write
instead, i.e. without the backslash at the end of the line, then none of the files inside of the folder 'a' will be synced, not even the files inside of nested directories. But it is really strage that the entire (blank) directory structure below the folder 'a' (without any file) will be synced to the sync target.
So far so good. The important thing appears to be the backslash at the end of the line in case you want to exclude folders.
The bad news is that folder exculsion does not work with wildcards. If you write
this does not mean, - in conjunction with code line no. 1 - that all target folders of the following structure will be fully excluded from the sync process:
If you are using wildcards, it appears to make no difference if you write
or
or
The entire folder structure of 'target' and its nested folders will be synced without any files.
1.) Excluding files
A file named 'New Text Document.txt' inside of sync root directory could be ignored by just adding the full filename:
This appears to prove that there are no issues with blanks.
... I did not do any further investigations yet