vpetersson Posted October 31, 2014 Report Share Posted October 31, 2014 In my setup, I have two laptops and two servers that I sync. One of the servers I sync with is in the cloud, and it is using encrypted keys. At first it seemed to work fine, but as it turns out, it started to choke on the Finder-files (which are still not in the default exclude list for some crazy reason despite being raised here in numerous threads for a long time). The normal remedy for this would be to add them to the IgnoreList. The problem however is that I have already added them there. Despite that, they keep syncing. If I add files to '.sync/IgnoreList', shouldn't they be excluded by the *sending* device as well as the receiving device? I.e. I can either chose to exclude a file on the sending device *or* on the receiving device. If it's added to the sending device, it should never make it to the receiving device. Quote Link to comment Share on other sites More sharing options...
RomanZ Posted October 31, 2014 Report Share Posted October 31, 2014 @vpeterssonWell, not actually. After you added files to ignore on sender, it can't simply delete them from the tree in memory, it starts saying to other peers that it do not have them. Though, other peers already know that these files exist and they want to download it. So, it is highly recommended to keep IgnoreList same on all peers (yes, we want to make it automatic in future - though it is not implemented yet). Quote Link to comment Share on other sites More sharing options...
vpetersson Posted October 31, 2014 Author Report Share Posted October 31, 2014 Thanks for the information, Roman. I'll see if I can resolve the issue by killing all nodes and simply adding them one by one and ensuring that they all have the Finder-files in the IgnoreList. That way, it shouldn't be possible for any of the nodes to be aware of these files. Quote Link to comment Share on other sites More sharing options...
trevellyan Posted October 31, 2014 Report Share Posted October 31, 2014 I'll see if I can resolve the issue by killing all nodes and simply adding them one by one and ensuring that they all have the Finder-files in the IgnoreList. That way, it shouldn't be possible for any of the nodes to be aware of these files. When you say "Finder-files", are you referring to OS X extended attributes, aka xattr? If so, you should be working with the StreamsList, not the IgnoreList. See http://sync-help.bittorrent.com/customer/portal/articles/1682051-alt-streams-and-xattrs-in-sync Quote Link to comment Share on other sites More sharing options...
vpetersson Posted October 31, 2014 Author Report Share Posted October 31, 2014 When you say "Finder-files", are you referring to OS X extended attributes, aka xattr? If so, you should be working with the StreamsList, not the IgnoreList. See http://sync-help.bittorrent.com/customer/portal/articles/1682051-alt-streams-and-xattrs-in-sync Oh, thanks. I did not know that. That said, wouldn't it make more sense to *exclude* the xattr files by default? My guess is that for the vast majority of the users, this is just useless overhead. Afterall, OS X will automatically generate these files on-demeand.Wow. Ok, so just merely minutes after removing the files from my StreamsList-file, the nodes got all in sync. Much appreciated @trevellyan. Quote Link to comment Share on other sites More sharing options...
trevellyan Posted October 31, 2014 Report Share Posted October 31, 2014 That said, wouldn't it make more sense to *exclude* the xattr files by default? My guess is that for the vast majority of the users, this is just useless overhead. Afterall, OS X will automatically generate these files on-demeand. It's not clear to me what the benefit of syncing them is. However, Sync 1.4.93 is working well for me with the default StreamsList, where version 1.3.109 would sometimes get hung up on xattrs, so I'm just leaving well alone. Quote Link to comment Share on other sites More sharing options...
vpetersson Posted October 31, 2014 Author Report Share Posted October 31, 2014 Odd. I'm on 1.4.93 too, but it was struggling. It does however seem to only be an issue with the node that I'm using the encrypted key with. Perhaps that is a known bug. Quote Link to comment Share on other sites More sharing options...
trevellyan Posted October 31, 2014 Report Share Posted October 31, 2014 It does however seem to only be an issue with the node that I'm using the encrypted key with. Perhaps that is a known bug. Yup - http://forum.bittorrent.com/topic/18036-extended-attributes/ Quote Link to comment Share on other sites More sharing options...
vpetersson Posted October 31, 2014 Author Report Share Posted October 31, 2014 Got it. Thanks. Oh well, I can live without syncing the attr data. Having the nodes in limbo because it chokes on these attr files -- not so much. Quote Link to comment Share on other sites More sharing options...
RomanZ Posted November 3, 2014 Report Share Posted November 3, 2014 @trevellyanMacOS stores some user-valuable information in xattrs - like, the fact that file is downloaded from internet or color-tags attached to files. Quote Link to comment Share on other sites More sharing options...
trevellyan Posted November 3, 2014 Report Share Posted November 3, 2014 @trevellyanMacOS stores some user-valuable information in xattrs - like, the fact that file is downloaded from internet or color-tags attached to files. Sure, I'm just not really interested in syncing those attributes, but I'm sure some people find it useful and I'm glad Sync can do it. Quote Link to comment Share on other sites More sharing options...
RomanZ Posted November 3, 2014 Report Share Posted November 3, 2014 @trevellyanYou can clean up the "StreamsList" file and they won't be synced anymore Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.