RomanZ

Administrators
  • Posts

    3,588
  • Joined

  • Last visited

Everything posted by RomanZ

  1. Hi @all, BitTorrent have launched official Synology package testing recently, so anyone interested - please feel free to join.
  2. @adam1v The changes in assigning file permissions policy are not planned in upcoming release.
  3. @Surfingnewport Sure, please do. Send it to syncapp@bittorrent.com, mention this topic and your nickname in the message body.
  4. @piotrnik It depends. Latest version of Sync for Android attempts to write a file more than 4Gigs if FS allow, though I get confirmed case when Sync was not able to save more-than-4Gigs file to EXT4 FS as Android did not let Sync do it.
  5. @Bitwise It just chooses the most fresh file time from DB. And even if file is deleted - record about it is still stored in DB. So currently the only way to reset the "last synced time" I can think of is re-adding folder.
  6. @Bitwise Thanks for this information. By the way - do you have uTorrent client? Does behaves in the same way as Sync?
  7. @MadCityWedge You need to "Disconnect" camera backup (i.e. fully remove it from Sync" and then you'll be able to add it as regular RW folder.
  8. @eikman2k Sync was designed to propagate all file changes - including file renaming and deletion. If you delete your file - it should be deleted from other peers as well - unless someone keeps it open and actively working on it. In this case you'll likely will receive updated version of file back.
  9. @kratochviljan The "Listening port" actually forces Sync to listen selected port and use it for all possible communications (it still will use different for outgoing TCP connections). Setting predefined host just indicates Sync that particular IP will have certain port open. It doesn't force remote Sync to open this port, and it does not prevent local Sync to use other means (Tracker, Relay, multicast, cache) to find other peers. @patoka If you disable tracker, relay and LAN search - sync still will attempt predefined hosts as well as look into it's cache of addresses (hold for 7 days by default).
  10. @kahunals Let's try to see what happens there. When you see that file transfer stuck - open app preferences on Android, and tap "Send feedback", put your e-mail we can respond to and put this topic link to message body as well as your huge file's name. Then agree to send debugging information together with feedback message. I'll try to track what happens to your file.
  11. @robertogl Could you please enable debug logs on your peers and let it run? If you encounter issue again - collect logs and send to me, we'll take a look on what is happening there.
  12. Well, root should have access to it. I wonder if you could collect and send me a full set of debug logs?
  13. @triplemaya Give me an e-mail when you want get back to your project - I'll help you in Sync setup.
  14. @hawkman I suggest checking what user runs btsync and what are permissions and owners for the folders DataVolume, shares, Public - the user who runs Sync might lack permissions to these folders.
  15. @blakev Usually you don't have to do anything - you should just click the link and Sync will add it. Though something went wrong in Sampsa's case and looks like his computer lacks of certain reg keys necessary for Links to function. Links were designed to be simpler to use than regular keys - though they are a bit more dependent on user's OS.
  16. @MadCityWedge Camera backup functionality was not removed in 1.4. Why can't you add folder anymore? Could you please describe setp-by-step what are you doing, and what happens? Couple of screenshots could also be great.
  17. @kahunals Sync for Android supports delivering files up to 4Gb. I wonder if your Android device has enough free space to store files?
  18. @Bitwise, @tommi It might indicate that certain folders contain files with incorrect modification time (in future). I suggest finding these files and fixing mtime as it can bring issues in future (they will overwrite any other files with same name on other peers as they are always "newer").
  19. @skywriter Yes, we'd like to implement background Sync for iOS in future. @geitje1 Well, this is not a corrupt file. This is a temporary file that is created Sync when it delivers new data. it was "corrupt" most likely because Sync did not finished data transfer yet.
  20. @triplemaya What are the OS involved? Are you sharing RO or RW keys?
  21. @Andarel Could you please elaborate how exactly the extensions of your files has changed? What kind of files you were syncing and if these files were in use while synced? When Sync is changing the file (=delivering from other peer) - it saves a copy to .sync\Archive subfolder - mind checking it for old copies.
  22. @Xaelias The use case it pretty much valid. In your case Sync should compare and make sure that F set of files already present on your B computer and then sync only G set of files. First of all - It is very unlikely that Sync "corrupt" your files - if files are not huge, Sync usually delivers them to a temp file with !sync extension and only when transfer complete - replaces the original file with !sync. Second - are you sure that transfer actually occurs? When Sync merges file trees, it may show a very rapid file transfer, though no transfer actually occurs. Third, your folder on A and B must have completely same folder structure and files positions. Otherwise (even 1 level folder difference) it will make a duplicate of everything. Fourth, could you please check if the FTP client and server you use do not change mtime of files? I.e. that the mtime you have on Debian is the same you got on Win8?
  23. @robertogl Most likely Sync is unable to access these files - either due to permission restrictions or because files are open by some other application. What are the file names which cannot be synced?
  24. @heliumhel force_https disables regular http access. It should simply redirect you from http to https same URL. Please look carefully in your browser - does it use HTTP or HTTPS when actually loading the page? Also, the pass prompted once and saved to a session cookie, so you'll need to restart your browser to get prompted again.