rwohleb

Members
  • Content Count

    1
  • Joined

  • Last visited

About rwohleb

  • Rank
    New User
  1. Based on the work of eseelke, erkr and others I was able to get btsync installed on a Zyxel NSA320. Make sure you already have FFP installed. http://zyxel.nas-central.org/wiki/FFP-stick Download the latest version of btsync for ARM (version 1.1.70 at the moment), untar/unzip the tar.gz file, and then place btsync at /ffp/bin/btsync. If you downloaded the file to your local computer you can SCP it to the NAS: scp btsync root@NSA320:/ffp/bin/Create the /ffp/start/btsync.sh file: #!/ffp/bin/sh# PROVIDE: btsync# REQUIRE: LOGIN. /ffp/etc/ffp.subrname="btsync"command="/ffp/bin/btsync"btsync_flags="--config /ffp/etc/btsync.conf"required_files="/ffp/etc/btsync.conf"run_rc_command "$1"Then set the start script to be executable: chmod u+x /ffp/start/btsync.sh The default config file can be installed by: /ffp/bin/btsync --dump-sample-config > /ffp/etc/btsync.confI recommend that you modify the config to move the btsync storage path out of the FFP root and onto one of your drives. The storage path will contain things like the sync.log which can get large and is accessed a lot, so a USB stick might not be the best place for it. "storage_path" : "/i-data/md0/.btsync"I ran into the unreachable web UI and 100% CPU issue that some people are reporting. What I found is that if you change the web UI port to something other than 8888, such as 8080, then this issue goes away. I'm not sure why port 8888 is unavailable on my NAS, but it appears that if btsync can't listen on the port, it gets into a loop that eats the CPU.