wiebel

Members
  • Posts

    6
  • Joined

  • Last visited

wiebel's Achievements

New User

New User (1/3)

  1. I have it in /usr/local/bin on all my linux boxes, no problem whatsoever. You might run in trouble using btsync without a given config, as the default ist to create a .sync folder in the directory where the binary resides. So a user call of btsync (without --config) will result in btsync trying to create /usr/local/bin/.sync which should fail as users normally aren't allowed to write there. Anyway I would also appreciate btsync respecting $HOME so it could create $HOME/.sync instead of <path of directory of btsync>/.sync which is indeed ridiculous. BTW. I use following line for upgrades in case anyone is interested: VER=1.1.48 ; curl http://syncapp.bittorrent.com/$VER/btsync_x64-$VER.tar.gz | gunzip -d - | sudo tar xfv - -C /usr/local/bin && /etc/init.d/btsync restart
  2. You should let your initscript fix this issue. I have one like https://gist.github.com/MendelGusmao/5398362 which starts a btsync process for each user in a given list and uses ~/.sync/config.json . There are many ways for root to start a process as a user, initscrips fpr debian usually use start-stop-daemon. "apt-get only works as root" is (almost)true on the one hand but utterly unrelated. Even if you don't use any initscript at all you can simply run the "apt-get installed" program as user. Take care, "@reboot" is not supported by all cron daemons, check your local manpage.
  3. It's also a Marvell chip as in the Dreamplug It's Marvell 88f5182 @500MHz cat /proc/cpuinfo Processor : Feroceon rev 0 (v5l) BogoMIPS : 331.77 Features : swp half thumb fastmult edsp CPU implementer : 0x41 CPU architecture: 5TEJ CPU variant : 0x0 CPU part : 0x926 CPU revision : 0 Hardware : QNAP TS-109/TS-209 Revision : 0000 Serial : 0000000000000000 Btw. the new version 1.1.22 runs fine again but also no syncing so we still have to wait.
  4. I have a Qnap ARM (Marvel chip) running debian and a raspi (Arch-Linux). I was able to run all Versions prior to 1.1.* on the Qnap but no syncing at all was possible towards the qnap. The 1.1.* Versions are segfaulting on the Qnap. Now I Mount my Qnap via NFS on my Raspi and run the btsync there. Awkward but at least it works
  5. Same here with Debian on ARM. (2.6.32-5-orion5x, armv5tel, QNAP TS-109)
  6. I'm running the ARM release (1.0.116 - 1.0.134) on my TS-109pro II running Debian squeeze. It comes up fine I'm able to login and configure my syncs, all seems good, except no files arrive. to be more specific here is what works: - All syncing from the TS-109 to any other computer - Syncing of the directory structure and even all symlinks from any computer to the TS-109 What does not work: - Syncing of actual data from any computer to the TS-109 The log has many lines like: " Torrent test.001 status: 137 error: <NULL> meta: 1 " Has anyone experienced anythig alike?