Brad@IO

New Members
  • Content Count

    12
  • Joined

  • Last visited

About Brad@IO

  • Rank
    Member
  1. That response doesn't clarify where we are at regarding older files overwriting newer files in Advanced folders. There's an increasing number of companies we deal with where discussion of Resilio sync comes up as an option and we always mention the problem with older files overwriting newer ones. It would be great to be able to know that issue has been 100% fixed, with no caveats. Are you saying: the issue with standard folders discussed in the thread is fixed but the specific known issue with Advanced Folders referred to by RomanZ still exists or the specific known i
  2. It would be good to have a clear clarification, but I guess for now we should assume that the problem still exists...?
  3. Hi Guys, bumping this old thread to see if there's new info. When I had problem with older files overwriting newer ones back in Oct 2015, RomanZ, confirmed that the issue <snip>...was fixed for Standard folders in 2.2.5 (while still exists for Advanced ones - its a bit more complex to fix it for advanced folders). As a result we've never used Advanced folders, but we would like to be able to take advantage of them. I've scanned the change logs several times since, but been unable to find any mention of a specific fix. Is this issue fixed for Advanced folder
  4. Thanks Artem. You've saved me again. :-) BTW thanks for the windows service fixes and also 2.3.2 fixed the RAM usage on the NAS. cheers
  5. Having read the forum postings and articles about IgnoreList (eg http://help.getsync.com/hc/en-us/articles/205458165-Ignoring-files-in-Sync-Ignore-List- and others), the wording leaves it unclear about the behaviour on existing syncs and propagation of the IgnoreList file itself. ie "How do I stop syncing certain files on EXISTING syncs?" Say I've realised that *.pyc files are syncing unnecessarily. I want to stop this on all the peers with that sync (BTW all read/write and all running via BTSYNC WINDOWS SERVICE). So my questions are: If I change the IgnoreList file on m
  6. @romanZ: Interesting. We've always picked STANDARD when we add a share, but it seems they've all been set up as ADVANCED folders. Maybe because the share window next presents a permissions option before you share the link. Am I right in thinking that if we see this permission option then we're setting up an ADVANCED folder? @great marko: found the manual instructions for updating BTsync on the Synology NAS. Done. Happy to test again, but will that only be useful if the folers are converted-to or re-shared as STANDARD?
  7. @great marko: The windows peers are running 2.2.5, but is there a simple method for updating the version running on the synlogy NAS? I haven't been able to work out how to update that "package" so far from 2.0.93. @romanz: standard folders AFAIK
  8. Any news on this? I've just discovered this massive bug and it's easily reproducable. It's a catastrophic scenario. New peers added with older versions of files simply overwrite all newer instances of those files on all peers! Wow. It's got nothing to do with clock syncing. Our tests have shown 10 year, 1 year, 1 month, 1 day, 3 hour old files overwriting files that are less than 10 min old. There's no hope of using BT sync in any kind of professional environment with this sort of issue. Can we get a formal response about this issue from support?