• Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by lux

  1. It sounds like he wants to use it to automate syncing his warezed files to his local PC from his torrent box, and if his torrent program does not only move finished downloads into the synced folder but does the actual downloading there, that would re-hash and re-sync in-progress downloads all the time, wasting boundless CPU time/electricity as well as probably wasting gobloads of bandwidth.

  2. Ah, my user did not have permission to write the .pid file. Now everything works, cheers :)

    And yes, I noticed the JSON errors in the sample config myself when I was first testing it. Thanks to that I now know JSON syntax again, hadn't used it in a while.

    By the way, while it's very forthcoming of you to also send me your replies via PM, you can see in the top right corner of this board's design that I'm subscribed to this thread :)

  3. From what I gather from other threads, putting IPs into the list of preset hosts defines them as "local". Might be getting this wrong though.

    Don't know if works at all there. I've done SSH tunneling before with my server but I don't need it for BTSync.

  4. He wrote some funky setup scripts (dpkg-configuration) that ask you to enter some initial settings (so you don't necessarily have to write your own JSON). His default binary path was "/usr/sbin/btsync-daemon" on my system, rather than for example keeping the binary named "btsync".

    His /etc/init.d/ scripts didn't work for me, don't know if that's because the setup ultimately failed for me or because of something being wrong with his script or....

    His launch script also makes sure you have "check_for_updates" : false, else it refuses to start.

  5. I can understand that you want to have this feature only in an "Enterprise" tagged version, but i disagree with you: It's NEVER a bad idea to sync file ownerships, even in consumer world.

    Is it just me or is it painfully obvious why it's a bad idea? I'm sharing files with my friend, obviously these need to be owned by his user on his PC and by my user on my PC...

    Speaking of platform-specific data (ACL) not getting lost on other platforms, has a very sexy approach.

  6. Unpacking btsync (from btsync_1.0.125-1_amd64.deb) ...
    dpkg: dependency problems prevent configuration of btsync:
    btsync depends on libc6 (>> 2.15); however:
    Version of libc6:amd64 on system is 2.13-38.

    dpkg: error processing btsync (--install):
    dependency problems - leaving unconfigured
    Errors were encountered while processing:

    ^<- didn't work on my Debian. is out now btw, the build there did work for me