fastfwd
-
Posts
11 -
Joined
-
Last visited
-
Days Won
1
Posts posted by fastfwd
-
-
Ok, I'll go first...
1.4.91 still has some little issues, but btsync's CPU usage on my Linux system, which used to be a steady 7-10%, is now practically zero while it's idle. Thanks!
I'm running 1.4.91 on one Win7/64 machine, 1.4.91-i386-glibc2.3 on a Debian Etch box, 1.4.83 on two more Win7/64 machines (soon to be upgraded to 1.4.91), and 1.3.109 on a WinXP machine. All the machines seem to be playing nicely with each other, and I haven't seen any new problems.
-
@fastfwd
Please use Glibc 2.3 build for now.
Thank you, RomanZ.
-
This was caused by gcc update. Since version 4.5 a completely new type of symbols was introduced - unique global symbol (GNU-UNIQUE). This means that older version of linker and gcc will not support such symbols.
_ZNSs4_Rep20_S_empty_rep_storageE is one of those symbols, which means you can't run it on older systems.
And glibc23 is working fine because it was build with older toolchain, without such symbols.
Thank you for the explanation. How will this issue be addressed? Will future i386 versions be built so that they will run on those older systems, or will we have to continue running the glibc23 versions, or will there be yet another variation -- i386 built with an older toolchain -- or something else?
-
On this system, BTSync-i386 version 1.4.75 crashes immediately on startup, exactly as version 1.4.72 does:
symbol lookup error: /usr/local/bin/btsync/btsync: undefined symbol: _ZNSs4_Rep20_S_empty_rep_storageE
The OS is what Netgear calls RAIDiator 4.2.26; it's Debian Etch (Debian 4.0) running on a ReadyNAS Pro. Kernel is version 2.6.37.6.RNx86_64.2.4.
My earlier error report for 1.4.72 is here: http://forum.bittorrent.com/topic/31281-btsync-1472-crash-on-linux-i386/
-
When starting BTSync 1.4.72 on a Debian box which had previously been running version 1.3.106 with no errors, I get:
symbol lookup error: /usr/local/bin/btsync/btsync: undefined symbol: _ZNSs4_Rep20_S_empty_rep_storageE
Perhaps there's some library that's not being properly linked?
-
I notice that the key will never use these characters: {0, 1, 8, 9}. Everything else ({2-7,A-Z}) gets expressed occasionally, but the other four characters are never used.
Any good reason for this?
-
Oh, I see. I misread "the Linux machine had a full disk" as a symptom of the problem rather than the cause of it.
-
I am using 1.1.70 on all machines.
The only linux machine (that is up 24/7) had a full disk. Other Windows 7 and Windows XP clients were getting corrupted (probably incomplete) files and sometimes even folders were disappearing.
Very annoying, but once I figured out the problem, the fever was over
And the problem was...?
-
There were no new features between 1.1.70 and 1.1.78, and likely only bug fixes. However, the fact that 1.1.78 isn't currently available suggests that the developers found a particular issue with it, and felt that 1.1.70 was the more stable option for users at this time.
If that is true, the developers should have re-posted the 1.1.70 build with a version number greater than 1.1.78, so that 1.1.78 installations would see a "new" version and upgrade to it.
-
not quite sure where you've got 1.1.78 from?!
1.1.78 was being served from http://download-lb.utorrent.com/endpoint/btsync/os/windows/track/stable for a day or two, then it was pulled down and replaced by 1.1.70. Looks like 1.1.78 was built on 13 September:
User Account Control (Uac) Prompt, Limited User
in Sync Troubleshooting
Posted
Change the value from 0104006a to 0104006e.