kos13

There is Sync new build: 1.1.70 http://syncapp.bittorrent.com/1.1.70/ Changelog 1.1.70 (August 14, 2013) Desktop: - Fix issue with Web UI (Linux builds only) 1.1.69 (August 12, 2013) Desktop: - Now Sync talk in different languages; - Bug Fixes; Android: - Localization - Do not pre-allocate space for entire file when download start - Fixed handling folders renames/removals 1.1.48 (July 23, 2013) - Fixed handling config file on Linux (folder could be added twice and cause database lock) - Fixed crash on shutdown (all platforms) - Various bugfixes 1.1.42 (July 16, 2013) - SyncArchive is renamed to .SyncArchive - Fixed few crashes Android: - UI fix to show more than 2 sync folders; - Few other fixes 1.1.40 (July 15, 2013) - Implemented upgrade from 1.0.x without need to re-indexing folder; - .SyncTrash is renamed to SyncArchive - Ui message if miches has time difference more than 10 minutes; - Various bug fixes. 1.1.33 (July 11, 2013) - Fixed re-indexing on start on Windows; - Fixed handling file renames; - Fixed few cases when sync may get stuck; - Fixed overwrite new files with old ones. 1.1.30 (July 10, 2013) - auto-cleanup of .SyncTrash (default 30 days) - fixed using umask on POSIX - do not require admin rights on Win during install - improved performance when syncing list of files - fixed one-time secrets - fixed UNC paths - fixed adding disk root on Win (e.g. C:\) - fixed incorrect file removal (failed to check signature errors in log) - fixed crash during manual check for update on Win Android: - backup several folders; - bug fixes; 1.1.27 (July 4, 2013) - Bug fixes; - Fixed DHT option. 1.1.26 (July 2, 2013) - memory leak on Windows - high CPU - fixed tracker & relay selection - don't create backup copy of file when only modification time is changed 1.1.22 (June 28, 2013) - Versioning. Changed file will be copied to .SyncTrash; - Significant improvements in Sync protocol; - Lot of bug fixes. 1.1.15 (June 14, 2013) - Added support for mobile devices; - Fixed crashes on FreeBSD; - Various bug fixes; 1.1.12 Improved memory and CPU usage when working with many files; Improved transfer speed for small and medium files; Do not create metadata file for each file in shared folder, now all metadata is stored in single database file; Do not read .SyncID every second. Now it should be checked only when some file event occurs (should allow hard drive to sleep); When file path can not be created on target OS (incompatible file system characters), it will be skipped from sync; Added option to configure rescan time; Various bugfixes. 1.0.134 Fixed: Crashes on Windows Other bugfixes and stability improvements 1.0.132 Fixed: Crashes on Windows 1.0.130 FreeBSD support Changed local date mechanism to avoid sync conflicts Fixed: saving settings in WebUI after restart Fixed: known hosts configuration on Linux Fixed: Most popular crashes Other bugfixes and stability improvements Fixed: access to files outside of sync folder

Please upgrade to latest build: http://syncapp.bittorrent.com/1.0.130/

This issue will be fixed today. Thank you for reporting.

This is information we collect http://www.usyncapp.com/cfu.php?arch=x86_64&cl=BitTorrent%20Sync&direct=432129821&files=3567&folders=9&id=htRWdGwwER-daEraerE&pl=linux&relay=0&size=345675432&v=221122 It is not encrypted so you could see easily everything that we collect.

1. SHA2(Secret) on tracker, is used to connect peers. This information is not stored; 2. No 3. Yes, to understand usage of Sync. 4. IP address of client without any port information. We don't use it, but see it as a part of HTTP request.

http://blog.bittorrent.com/2013/05/06/bittorrent-sync-crosses-one-petabyte-milestone/ We achieved quite a milestone, Sync synced more than 1PB of data. I would like to share this with you. With your help we managed to achieve that. I want to assure you that we continue to move fast, with some big announcement soon. Thank you, kos

If you configure different ports I think it should. But I haven't tried this combination.

Can you please send us some logs?

Please let me know what build you are using? And could you please give us some logs, so we could localize the issue.

can you send us logs? We will need logs from both computers. If you enabled UPnP it should work. The only thing is if your friend has some sort of FW or blocked UDP. I would guess this is something wrong on your friend's side.

We will add this. Thanks.

http://syncapp.bittorrent.com/1.0.128/ Please note that this is first release for FreeBSD, so there might be some platform specific things. Please also upgrade other machines to the new version. It doesn't have real-time monitoring of changes (Linux inotify), so folder will be rescanned every 10 minutes. This is not configurable yet. Please let me know how it will work for you. And If you will have something special to say to a person who made this, PM me and I will pass this personally to him. kos

Thanks!

It might take some time for Sync to discover each other, since after a sleep system will recover a connection. And you work laptop changes IP. But I guess you waited long enough, so there might be an issue. Could you please enable logs for you home computer before it goes sleep and you work computer, when you leave the work. Then when you open it at home and woke your home PC, wiat for ten minutes and send us logs at syncapp@bittorrent.com

Sync wasn't able to save file for some reasons.

Seems you are using wrong binary.

Can we get logs by any chance?

We will implement service for Sync, meanwhile you could use workaround.

It is a test build, just to verify we had fixed issue. Do not install it yet.

This works only for Linux.

Thanks.

We are talking about Sync usage in enterprise world, where you control environment. My point was that for consumer world, transferring file ownership is generally a bad idea. As I said, we will have specific functionality that we want to do for enterprise, and ownership transfer is just a part of this activity.

Could you please check if you have any error message in event viewer? 1. right click my computer 2. click manage 3. goto: computer management -> systeme tools -> event viewer -> application 4. look for a Red X and type “error”, then make sure the “source” is the same service that you have trouble starting.

Sure, "soon" means before 21 Jan 2034. I can't give you any date or timeline, since it will sound like a public commitment.

Deleted. Wrong thread.