mcgroarty

Members
  • Content Count

    13
  • Joined

  • Last visited

About mcgroarty

  • Rank
    Member
  1. Thank you, this worked. Resilio really needs to ape whatever behavior prevents the countless other startup programs from exhibiting this problem. If users are going to trust Resilio with important information then it can't adopt the look of abandonware. That's what a year old UI glitch looks like.
  2. Are you suggesting that Windows 10 users need to manually exit Resilio sync before every single reboot?
  3. Also, if it's relevant: On all three machines and in all three folders, I added "*.lnk" to .sync/IgnoreList I don't want Windows shortcut files to be synced to other Windows machines, or to the Mac where they are meaningless. I also turned off the option for keeping deleted files in a special folder. Other than those two things, entering my license key, and resizing the window, all settings are the defaults. Edit: I removed the sync, established it again, and the mystery errors are gone. The window still opened at every startup, but as a workaround I disabled the Windows 10 feature that relaunches previously running apps after restarts. Apparently Resilio can't tell that it's being relaunched this way, per another thread.
  4. Edit: Solved, as per my reply below. I'll leave this in place in case anybody else encounters something similar. I've installed Resilio on a couple Mac machines and one Windows machine (so far). I wish to sync my Downloads, Desktop, and Documents folders across all three. Everything is going well on the two Mac machines. But the Windows machine opens the window at every restart, and shows "99+" sync errors. However when I click on the 99+ I can't see a list. It comes up empty. Clicking "ignore all" doesn't prevent this from happening at the next reboot. Is there a way around this? I'm not even curious what the original errors were. These are from the initial sync, and I know there were a lot of resource forks, etc which couldn't be copied over. If there's a way to make Resilio forget past errors and only warn going forward, that would be fine. Also, of note, those two "Status" indicators never proceed from 100% to a green checkmark. Is that expected?
  5. Is it safe to use BitTorrent Sync on a removable volume, such as a USB disk or a network filesystem? How does BitTorrent Sync handle cases such as starting while the volume is unavailable and having the volume come online after BitTorrent Sync is already started? Or what about the case of the volume being unmounted while BitTorrent Sync is already running? I searched and found threads from early 2013 where this was declared problematic, but something the team would work on. I didn't find any updates. To be clear, this is not a case of wanting to sync between a removable volume and a fixed volume from the same host - that's a different topic that comes up often as well.
  6. The answer should be to get it working well in the default mode, not to turn it off by default if someone isn't confident about the implementation. Extended attributes are necessary for some apps to function properly or efficiently. Maybe not your apps, but there's a reason this nut got cracked early with the major cross-platform sync services. From my past experience, offering up specific, simple steps to reproduce problems that bother you and putting them in a support ticket as a bug report gets fast results. I had five or six issues fixed within 1-2 releases... sometimes they offered a developer build within the week! This team moves quickly.
  7. Thorough answer. Thanks a ton, RomanZ. It sounds like a great implementation. I don't know about others, but for me this was one of the last things tying me to Dropbox.
  8. The release notes say that the Mac now supports extended attribute syncing. Wonderful! Has anyone spent time with these? I'm curious if you can answer any of... * Do extended attributes survive in a mixed environment? (Mac and non-Mac) * If extended attributes are stored on non-Mac machines, where are they kept? * Are extended attributes synced separately from files? For example, if I set Finder colors on 50 1G files, does it have to re-checksum 50G of data? Just the metadata? Any catches or nice surprises?
  9. This may come a bit late for you, but I got that exact same error when everything but .SyncID was writeable by the btsync user on a Synology box. I couldn't find any log file that specified what file was wrong - will file a bug accordingly.
  10. Scenario: 1. I set up BitTorrent Sync on a folder one machine A 2. I manually copy this folder to machine B 3. I install BitTorrent Sync on machine B and sync the same folder Note that the manual copy (rsync, cp on a network share, etc) would include the .SyncID from machine A on machine B. Is this safe?
  11. How does BitTorrent Sync handle a peer that comes back online after extended absence? For example: System A and B have a file: Example.rar System A is powered off System B erases Example.rar 30 days pass System A powers on again, now with 30 day old sync info Will System B know to *not* receive Example.rar as if it were a new file? How? This is a pet peeve with DropBox, where thousands of files I've deleted can spontaneously resurrect on my main machine when I power up my travel laptop.
  12. Use the filesystem change notification API available on major OSes. This allows watching a local folder for changes rather than re-crawling. Changes are detected instantly, and there is no constant performance penalty. I don't know if a single cross-platform library exists for this, but the interface is pretty simple on each platform. Seek info on the FSEvents API on Mac, FindFirstChangeNotification on Windows, and inotify on Linux. Dropbox uses this approach. Even with 1.5 million files, Dropbox remains idle when no changes have been made. If it were crawling these folders every ten minutes, it would be unusable on a laptop or a desktop with a spinning disk.
  13. Rescanning of large folders can crater system performance. This is why all major OSes have an API for subscribing to changes to local volumes. By receiving notifications when a watched folder changes, there is no need to scan folders more than once. Should BitTorrent Sync be using this? I don't know if a single cross-platform library exists for this, but the interface is pretty simple on each platform. Seek info on the FSEvents API on Mac, FindFirstChangeNotification on Windows, and inotify on Linux. Dropbox uses this approach. Even with 1.5 million files, Dropbox remains idle when no changes have been made. If it were crawling these folders every ten minutes it would be unusable on a laptop or a desktop with a spinning disk.