Search the Community

Showing results for tags 'gentoo'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Resilio Sync
    • Sync General Discussion
    • Sync Troubleshooting
    • Sync for NAS (Network Attached Storage)
    • Sync Stories
    • Developers
    • Feature Requests

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 2 results

  1. Hello. I have problem with btsync. I have tested it last time today with Linux x64 1.3.94 version. It is starts, reports no error, but do not do any work, do not write anything into log. Also, it exits only on second Ctrl-C or SIGTERM. I turned on debug: ~ $ cat ~/.btsync/debug.txtFFFFBut the log file still do not appear. If I start it in foreground mode, I see this: ~/.btsync $ /opt/btsync/btsync --config /etc/btsync/config --nodaemon --log sync.logBy using this application, you agree to our Privacy Policy and Terms.http://www.bittorrent.com/legal/privacyhttp://www.bittorrent.com/legal/terms-of-usetotal physical memory 536870912 max disk cache 2097152Using IP address XXX.XXX.XXX.XXXtest sha1: AE5BD8EFEA5322C4D9986D06680A781392F9A642test sha2: 630DCD2966C4336691125448BBB25B4FF412A49C732DB2C8ABC1B8581BD710DDtest aes: 0A940BB5416EF045F1C39458C653EA5A07FEEF74E1D5036E900EEE118E949293^C^CIt does nothing after "test aes: ...". If I run strace on the process, which stuck in that way I see this: ~ $ strace -p 28735 -ffProcess 28735 attachedrestart_syscall(<... resuming interrupted call ...>) = -1 ETIMEDOUT (Connection timed out)futex(0x4501920, FUTEX_WAKE_PRIVATE, 1) = 0futex(0x450194c, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 5, {1398668412, 247165000}, ffffffff) = -1 ETIMEDOUT (Connection timed out)futex(0x4501920, FUTEX_WAKE_PRIVATE, 1) = 0futex(0x450194c, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 7, {1398668472, 247366000}, ffffffff) = -1 ETIMEDOUT (Connection timed out)futex(0x4501920, FUTEX_WAKE_PRIVATE, 1) = 0futex(0x450194c, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 9, {1398668532, 247562000}, ffffffff) = -1 ETIMEDOUT (Connection timed out)futex(0x4501920, FUTEX_WAKE_PRIVATE, 1) = 0futex(0x450194c, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 11, {1398668592, 247750000}, ffffffff) = ? ERESTART_RESTARTBLOCK (Interrupted by signal)--- SIGINT {si_signo=SIGINT, si_code=SI_KERNEL, si_value={int=943012408, ptr=0x4b534d2038353a38}} ---rt_sigaction(SIGINT, {SIG_DFL, [], SA_RESTORER, 0x724b0ce15b10}, NULL, 8) = 0rt_sigreturn() = -1 EINTR (Interrupted system call)futex(0x450194c, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 11, {1398668592, 247750000}, ffffffff) = ? ERESTART_RESTARTBLOCK (Interrupted by signal)--- SIGINT {si_signo=SIGINT, si_code=SI_KERNEL, si_value={int=943012408, ptr=0x4b534d2038353a38}} ---+++ killed by SIGINT +++Config file have nothing special: { "device_name": "user", "listening_port" : 14444, "storage_path" : "/home/user/.btsync", "pid_file" : "/home/user/.btsync/btsync.pid", "check_for_updates" : false, "use_upnp" : false, "download_limit" : 10240, "upload_limit" : 10240, "webui" : { "listen" : "127.0.0.1:8888", "login" : "admin", "password" : "password" } , "shared_folders" : [ { "secret" : SECRET, "dir" : "/home/user/sync", "use_relay_server" : true, "use_tracker" : true, "use_dht" : true, "search_lan" : false, "use_sync_trash" : true, "known_hosts" : [ ] } ]}
  2. I'm using gentoo, so i made an ebuild + init script for btsync. If someone wants to use it, it's on my overlay: http://git.btbn.de/gentoo-overlay.git/tree/net-p2p/btsync It has an init-script and conf.d file, so you can start btsync as system daemon on startup. The configuration file for the system daemon resides in /etc/btsync.conf You have to configure the user(most likely your normal system user) as which btsync is run in /etc/conf.d/btsync The only real important setting is the pidfile, as the init system relies on it to be created in the right place, so don't change the preset path.