Latest Sync Build: 1.1.70


Recommended Posts

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

Link to comment
Share on other sites

Great Guys!

Is there something i need to do so i can run this on freebsd?

When i wget the tar, untar, chmod 777 the file and run ./btsync i get the following error:

ELF binary type "0" not known.

./btsync: Exec format error. Binary file not executable.

Do i need to brandelf the binary?

Running from a jail in freenas 8.3

Link to comment
Share on other sites

Great Guys!

Is there something i need to do so i can run this on freebsd?

When i wget the tar, untar, chmod 777 the file and run ./btsync i get the following error:

ELF binary type "0" not known.

./btsync: Exec format error. Binary file not executable.

Do i need to brandelf the binary?

Running from a jail in freenas 8.3

It sounds like you installed the Linux binary, not the FreeBSD binary. I'm running build 128 on FreeNAS 8.3.1-p2 (but not in jail).

Link to comment
Share on other sites

You are right... sorry for my stupidity

I noticed that version 131 is out, what changed?

Build 131 hasn't been officially announced yet on the forums, so it's just a test build to see if it fixes specific problems users are encountering. I just updated my FreeBSD/FreeNAS to build 130 from 128. I'm not going to update again because I want to see the auto-update mechanism work when BitTorrent officially releases.

Build 128 was the first FreeBSD build.

I'm sure Build 116 is still the most prevalent version "in the wild" because BitTorrent hasn't pushed the newly released Build 130 into the auto-update mechanism yet.

Link to comment
Share on other sites

It sounds like you installed the Linux binary, not the FreeBSD binary. I'm running build 128 on FreeNAS 8.3.1-p2 (but not in jail).

Just tested 131 and all goes well until the files are tranferring, after a couple of seconds i get a kernel panic. Tried it in jail and in the normal file system.

Link to comment
Share on other sites

Post output of 'cat /etc/version; echo; uname -a; echo; file btsync; echo; ./btsync --help | head -n 1' so BT can have all the details of your system. Build 128 and build 130 run fine on mine:

FreeNAS-8.3.1-RELEASE-p2-x64 (r12686+b770da6_dirty)

FreeBSD x.y.z 8.3-RELEASE-p7 FreeBSD 8.3-RELEASE-p7 #1 r249203M: Sat Apr 6 09:28:27 PDT 2013 root@build.ixsystems.com:/tank/home/jpaetzel/fn8.3/freenas/os-base/amd64/tank/home/jpaetzel/fn8.3/freenas/FreeBSD/src/sys/FREENAS.amd64 amd64

btsync: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), dynamically linked (uses shared libs), stripped

BitTorrent Sync 1.0.130

EDIT: corrected to /etc/version.

Link to comment
Share on other sites

FreeNAS-8.3.1-RELEASE-x64 (r13452)

FreeBSD x.y 8.3-RELEASE-p6 FreeBSD 8.3-RELEASE-p6 #0 r248141M: Sun Mar 10 16:35:05 PDT 2013 root@build.ixsystems.com:/home/jpaetzel/8.3.1-RELEASE/os-base/amd64/tank/home/jpaetzel/8.3.1-RELEASE/FreeBSD/src/sys/FREENAS.amd64 amd64

btsync: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), dynamically linked (uses shared libs), stripped

BitTorrent Sync 1.0.131

131 is offline atm, i am going to try 132 (132 is working perfect on my pfsens firewall btw, not the most secure thing to do i know but realy cool i CAN do it!, i realy love the sync app)

Link to comment
Share on other sites

There is Sync new build: 1.0.130

[..]

Fixed: access to files outside of sync folder

Can you please advise on this fix? Upon selecting "Add folder" the webui is still listing '/' vs 'storage_dir'.The daemon is running under the related system user, even went as far as copying the binary to their storage_dir and running it there but no dice.

Am I mistaken in thinking it's the same chroot issue I previously pointed out?

Link to comment
Share on other sites

Can you please advise on this fix? Upon selecting "Add folder" the webui is still listing '/' vs 'storage_dir'.The daemon is running under the related system user, even went as far as copying the binary to their storage_dir and running it there but no dice.

I think that fix had to do with an exploit that would allow BTSync to access files outside of the shared directory. It is unrelated to your issue.

Link to comment
Share on other sites

Whats new in 1.0.134?

1.0.134 hasn't yet been publicly announced/released - when - or rather, if - it is, I'm sure release notes will follow. At time of writing the latest official release is 1.0.132, and therefore general users should not be encouraged to use a later build until its availability has been officially announced/the build has been officially linked to.

UPDATE: 1.0.34 has now been officially announced! :)

Edited by GreatMarko
Link to comment
Share on other sites

When will upgrade be possible ?

Installing 1.0.134, already having for instanse 1.0.99 installed leaves me with the rather odd behaviour, that I need to create all shared folders all over.

On top of that, I find it problematic, that two versions can be installed at the same time.

Currently have 1.0.99 and 1.0.134 installed side by side.

05.17.2013-19.18.png

Edited by stallemanden
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.