RomanZ

Administrators
  • Posts

    3,588
  • Joined

  • Last visited

Everything posted by RomanZ

  1. @sebknzl, @scus, I'll check why do we escape characters and if this can be changed. However, the RFC4627 allows character escaping, i'm citing:
  2. @BlacklightJDR, BTSync has a database where it stores service data (like, directory tree and hashes for all the files). It also stores a "change time" for every file and folder. Change time might differ from file's mtime and usually indicates user's operation on the file: deletion, replacing file with the older version, etc. When deciding which file to store, BTSync relies on change time, not on mtime. For example: your sync dir contains a file a.txt, modified on 2014-01-15. It is synced to all your peers. When you add directory to BTSync, change times will be equal to files mtimes. Today, on 2014-04-15 you decide that the synced version is not something that you want, and you replace a.txt with older a.txt modified on 2014-01-01. In this case, BTSync remembers that the change time of a.txt is 2014-04-15 and it is definitely newer than 2014-01-15 of other instances of a.txt on other peers. So BTSync will distribute older file, because you (user) decided that it is more important for you.
  3. @antimojv, The manual still does not address the issues i've highlighted. rsync distinguishes some "safe" and "unsafe" symlinks for themselves, but I believe it is not applicable in BTSync case: people want symlinks to point outside of the sync folder (main usage scenario - accumulating all backup data in one folder).
  4. unsignedint, Could you please open a web developers console (javascript console - depending on your browser) and send me what is happening in console? It looks like javascript can't connect to the core. @hungarianhc, Do you see the <PID>.core file in btsync directory (or in .sync subdir)? If yes - please provide the file to me. Thanks! Also, can you please share the details of your setup / environment so we can try to reproduce your crashes in the lab?
  5. @vocatus, Thanks for the feedback! The peer limit was not reduced in 1.3, it stayed the same - 50 peers. However, there were indeed major protocol changes in 1.3 - now BTSync contacts tracker server over TCP, and prefers TCP in LAN. Could you please collect the logs from your peer so we can check what is going wrong? Please make sure to set log_size to ~500 as you'll have huge amount of records in a log due to numerous peers.
  6. nesreb, What about the log from second device (and the re-writed filename)? Thanks!
  7. sparda79, These apps are subjects for same limitations as BTSync. Are you sure that you did not root the device? Once rooted - you can easily overcome the limitation.
  8. mixmix, It looks to be a limitation of the filesystem, not the BTSync. BTSync simply can't create this file on your Linux machine.
  9. Klausemann, Thanks for the logs. I'll get back to you when analysis is done.
  10. @Tepid, Please try to open folder preferences on your PC in BTSync (the one you are backing up photos to), and tick the checkbox "Restore modified files to original version". It should re-sync pics once you delete or change them.
  11. Jack Nihil, Another thing to try is a new version of Android client, 1.3.20 - which may resolve your issue.
  12. Try playing with "Allow Mobile internet" setting in BTSync preferences.
  13. dilbert, Do you mean that BTSync constantly updates mtime of your Sync folder or something else? If yes, usually it indicates that some events are happening on other peers. Could you please try to shut down other peers and see if issue persists?
  14. Jimmy, I guess you've checked simple stuff (like, Mobile Data is allowed, waited for auto sleep period, etc.). Send me a feedback with logs, put a link to this topic in feedback form to make is easier. Thanks!
  15. Great, glad to hear now it is working. We'd like to make sync running in a background on iOS, but there are bunch of limitations by OS itself.
  16. thesoul214, It might happen that BTSync does not receive OS notifications on file change and have to wait for full folder rescan. Could you please submit a feedback from your Android phone? Please describe an issue in feedback form (and provide a link to this topic for reference) and include logs so we can see what's happening. Thanks!
  17. JimKnopf, Thanks for reporting - we'll continue investigation, please cooperate with our Support.
  18. CrayTo5, Auto sync does not affect discovery options. If it is set, it will simply grab all the files from other peers and deliver to your Android. If it is reset, if allows you to select which files to download - and will seed to other peers only downloaded files. Pause actually pauses current upload/download operations, regardless if you are syncing auto or selectively. While selective sync (=non-auto) allows you to download only those files you choose.
  19. @scruffyfox & @all, There are several peculiarities around going over symlinks as over folders. Let me make a list. 1) Symlinks are ruining tree-shape of the directory structure. They can wrap directory structure into itself. 2) Symlinks can drive BTSync out of directory (and store in general much more information than user expect) 3) Symlinks can bring BTSync to some network location which contains more info than expected 4) Symlinks can bring BTSync to a filesystem which is not compatible with current FS. 5) <probably some other peculiarities which i'm missing right now, but you also can guess> How do you expect (or find useful) for BTSync to deal with such issues?
  20. Jimmy, Thanks for the feedback. There was a serious battery usage optimization in 1.3.20.
  21. @okibcn, Thanks for reporting, we'll see how mtime validation can be improved in future.
  22. Daycaster, Try swiping downloaded file to left.
  23. @Bravo79, You can use API (see "GetFolderPeers" command). When it shows upload and download values zero - it means it stays in sync with selected peer.
  24. @throwawaytomorrow, Currently there is no such possibility, but it is on our roadmap to add it.