• Content Count

  • Joined

  • Last visited

About binarybana

  • Rank
  1. I like the simple downloads available at but it'd be great to have a 'latest' folder symlink that always points to the latest version. ie: My reasoning: in my system setup scripts, I wget btsync but I manually have to change the link to pick out the newest version everytime it comes out. Thanks!
  2. So I have ".git" in my .SyncIgnore on all my machines, and have had it this way for quite some time, but I've noticed that over time the machines will come 'off sync' and eventually get some files that don't sync (although normal files continue to sync fine). Logs on all machines have entries similar to: [20130718 23:40:15.126] State sync finished for folder /home/bana/GSP [20130718 23:40:15.222] LoadTorrent: requesting to load file research/samc/class-paper/.git/refs/heads/master which is modified on disk (cur:1376584154 stored:1376583655) - rejecting until file info is updated [20130718 23
  3. I noticed when rebuilding my sync index on upgrading to 1.1.26, that indexing will often force my hard drive into seeking I/O modes (I can hear the disk head thrashing, 13MB/s read speeds, and mostly IOWAIT CPU states), and then randomly switch to sequential reading (silent disk, 80+MB/s read speeds, and less IOWAIT). You can see the behavior in the attached resource graph (blue is CPU, dark blue is IOWAIT, and orange is HD read): It seems like this would be relatively easy thing to fix?
  4. I wasn't seeing the notify messages in the log either. I'd recommend turning on debug logging (make a file called debug.txt in the .sync folder where your log is, and add the text FFFF to that file). Also, you could try updating to the pre-release 1.1.15.
  5. For what it's worth, the Free Software Foundation (FSF) has an open source Bittorrent Sync clone as one of it's priority projects:
  6. It should work for any type of file, is there any reason in particular you are worried about .pst's?
  7. Sounds really exciting kos13! Although I would caution that when it comes to file syncing, rock solid stability and robustness usually trumps feature set. So don't put the cart before the horse.
  8. When I was first testing .SyncIgnore, I made a new empty folder, made a few dummy rules and then verified that it worked the way I wanted it to. You might try that to reduce your debug cycle time , and then once you have that working, you can try with a nearly empty ecryptfs mount point too.
  9. I can confirm that .SyncIgnore is working on x64 linux with version 1.1.15. Did you try one at a time? I added two simple rules: .git build and it successfully ignores any folder named .git or build and everything under these directories.
  10. @kos13: It turns out that /home/jason/syncapp/GSP/papers/12-fall/bma-related is actually a broken symlink to a non existent folder. So in that sense it does not have permission to write. Also, the (broken) symlink itself is fully owned by the user that SyncApp is being run under. And I think it is the case that the symlink is broken on one client, but still functioning for the other (as it points to somewhere outside of the SyncApp controlled folders).
  11. I couldn't find a bug tracker and I didn't find anything in a forum search, so I thought I'd put my problem here: When trying to sync two clients on a local network, it gets stuck in an apparent busy loop where the SyncApp client is using maximum bandwidth and growing the logs with repetitive entries of: .... [20130208 10:28:01] ReadFile error: [20130208 10:28:01] IO Error:2 line:382 align:-99 pos:-99 count:16384 actual:0 [20130208 10:28:01] ReadFile error: [20130208 10:28:40] Error opening "/home/jason/syncapp/G