Osiris

Members
  • Content Count

    29
  • Joined

  • Last visited

About Osiris

  • Rank
    Member
  1. I confirm: remove the .sync folder & start btsync. I had to do this 2x because I interrupted the wizard by exiting the browser.
  2. Already fixed? I still hit the same issues today, with todays download from https://download-cdn.getsyncapp.com/stable/FreeBSD-x64/BitTorrent-Sync_freebsd_x64.tar.gz So that's 2.0.93.
  3. I must concur with dgl289. No http proxy is sad, since it's the only way to proxy over here. Allthough ... when I set it to https, I am able to connect to the update site (which otherwise is blocked or gives a timeout, both without proxy as with the socks proxies). Whatever I try, I cannot get it to work. I've added a predefined host, I've tried all forms of the proxy. Should I check whether our proxy supports http connect ? UPDATE : in response to florentm: Using proxifier & my ssh tunnel, I'm able to route all btsync traffic through the tunnel, making the sync function. I've added a proxification rule for the btsync.exe app to any host on any port throught the http proxy on port 8080 (which is our corporate proxy).
  4. Hi, Since the (manual) update to 1.4.72 on my qnap I have a strange issue where I cannot click the share or edit buttons on existing sync-folders. The buttons actually appear on the header bar when I hover over the sync folder. When I move to the header bar to click the buttons, they disappear again (since I'm not hovering over the folder). What can I do ? UPDATE : This only occurs in the latest Firefox. In Chrome & IE it works fine.
  5. at 1.2.82, I'm experiencing this error, even when chmodding the folder to 777 when I mount the map to /something I can add it in btsync. not when I use /mnt/e/share/something. Weird stuff edit : had to restart btsync deamon after chmod.
  6. Any updates here ? Experiencing similar problems after 1.2.82 upgrade
  7. Osiris

    log size problem

    +1 Also need log file size limit. I'm syncing 8TB between nasses. my logfile is 25 GB atm.
  8. Not trying to necromance this, but ... Is there a way to automatically remove files from destination folders if they're not present on the read-only source ?
  9. Syncing 6TB of data from freebsd64 btsync on nas (FreeNas os) to ARM btsync on another nas (QNAP QTS 4.0.2 os). Syncing succesfully done. Logfile : 10GB. Any method to cap its size ?
  10. Osiris

    Latest Sync Build: 1.1.70

    Can this topic be un-pinned or have its title changed ??
  11. Osiris

    Wishlist (Archive)

    Totals : how much is synced / to be synced on all folders combined. Either on top of bottom, preferably configurable.
  12. Osiris

    Can't move files without deleting?

    seconding. I'm syncing 4.1 TB from one source to 2 destinations. Rearranging causes massive unnecessary traffic.
  13. From ubuntu to my mapped nas find /nas -iname ".syncarchive" -print0 | xargs -0 -I{.} find {.} -mindepth 1 -maxdepth 1 -exec ls {} \; -exec rm -R {} \;
  14. Osiris

    Two of my shares won't sync completely

    Update. Still syncing. Less than a terrabyte to go. Where can I find info on the whole syncing process ? Can't seem to find it in the docs. It seems some .!sync files are still being created on my read-only destinations. I assume these files are to be considered in progress. Yesterday, there were different ones on my destination but also 1 on my source. This is weird since there's no two way syncing being done. I'm assuming that syncing of the (large) file started while the file was being copied to the system and the .!sync file was then created somehow. I'm going to prudently conclude that this one file was the only problem.
  15. Osiris

    Two of my shares won't sync completely

    You cannot begin to imagine how much this has helped me. I ran this on both machines find /mnt/raid6/video/ -name "*.\!sync" -exec rm {} \;and restarted the btsync processes. Syncing resumed. a massive +1, if u ask me. I'm talking about a sync between a freebsd (Freenas 9) and my qnap. Had to run the line on a mapped drive from my ubuntu server to the qnap nas, since their find command doesn't allow the -exec. So In my opinion, case sensitivity has nothing to do with it. It also means that everything I said before was wrong or insignificant. Hurrah !