gr0undzer0

Members
  • Posts

    5
  • Joined

  • Last visited

gr0undzer0's Achievements

New User

New User (1/3)

  1. You may have gotten the 10 minute thing from : How soon does synchronization start? When a file is added to the shared folder, the changes start syncing immediately (due to system peculiarities, sync on Mac OS X 10.6 may be delayed up to 10 minutes). If you change a file inside a shared folder, sync will start after the file is saved and/or closed. Could OSx be that close to freebsd?
  2. Fair enough I couldn't find it anywhere either.
  3. I read the thread and it seems like there is NOT supposed to be a time interval between syncs. Can anyone point to an article that says otherwise for freebsd? I 've looked and not seen one.
  4. Thanks for responding affinity! Is that only applicable to the freebsd build ? That would explain why its one sided.
  5. Problem: Sync from my linux box to freebsd is almost instant Sync the from freebsd to linux only happens when a "periodic check" happens according to the logs. So for instance I put a file on the freebsd box at 00:17:00 and it doesn't show up on the other box until 00:20:00. When the following shows up in the logs: Logs: SyncFilesController: started periodic scan [20130419 00:20:48] SyncFilesController[file updated]: processing file /Rhodes/takesAReallyLongTime [20130419 00:20:48] New torrent created for file takesAReallyLongTime mt: Setup: I have a Linux box with the webUi on. It's setup with all the options unchecked accept delete files to .SyncTrash. The folder is connected to 10.0.0.24:1200 I have a freebsd box running with the following config: { "device_name": "hostname" ,"listening_port" : 1200 ,"storage_path" : "/opt/btSync/.sync" ,"check_for_updates" : false ,"use_upnp" : false ,"download_limit" : 0 ,"upload_limit" : 0 ,"shared_folders" : [ { "secret" : "the same secret i coppied out of the web ui" ,"dir" : "/Rhodes" ,"use_relay_server" : false ,"use_tracker" : false ,"use_dht" : false ,"search_lan" : false ,"use_sync_trash" : true ,"known_hosts" : [ "10.0.0.22:1200" ] } ] }