nop

Members
  • Content Count

    37
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by nop

  1. How many files are you trying to sync?

     

    I heard on a podcast,that someone tried to sync there giant family photo library that contained tens of thousands of files. That it just killed their home server because it had to rescan every single files over and over again. But this was when BTsync first came out. So I bet there has been improvement.  

     

     

    :D  :D  :D

    Even Boeing 747 can't kill a good server :)

     

    In all modern operating systems all frequent read\write operations on HDD are cached in computer RAM. And each HDD has internal cache too! So don't worry about "rescan operations". Windows Explorer doing this always for a lot of system files right after powering on the pc. ​

    http://en.wikipedia.org/wiki/Disk_buffer

    http://msdn.microsoft.com/en-us/library/bb742613.aspx

    http://www.wikihow.com/Change-Process-Priorities-in-Windows-Task-Manager

  2. Did someone get the proxy support working? I established a SOCKS5 proxy with SSH and "DynamicForward", I see attempts to connect to 54.225.100.8 port 3000, but connection fails. It also says "only socks5 connect supported" from SSH, but in btsync I activated socks5!

    Have you checked your ssh socks5 with other applications?

    Try to test with curl. Here is an example:

    curl --socks5 127.0.0.1:8080 http://asdf.com

     

    Good luck :)

  3.  

    On another system (15 folders, 20,000 files) btsync uses about 2% CPU, which I consider a normal value.

     

     

    As i understand - first system is NAS, and second system is NAS too?

     

    CPU usage depends from: CPU architecture, number of cores, number of supported instructions (SSE, AES) etc.
  4. All done except step 11. When I try I get this message:

    "service btsync does not support chkconfig"

     

    This happens because chkconfig reads the startup script named btsync and can't find the line which 

    starts with "# chkconfig:".

     

    Example:

     

    #! /bin/sh

    # /etc/init.d/btsync

    # chkconfig: 2345 80 05

     

    Numbers after "# chkconfig" provides information about set of levels on which daemon should run and start\kill priorities that should be used.

     

    Hope this will help :)