doodee

New Members
  • Content Count

    8
  • Joined

  • Last visited

About doodee

  • Rank
    New User
  1. Hi all, Long time user here, but just now seeing if I can use sync to access my data stored on my NAS. I have a share on my NAS that has all my scientific data, about 6TB and 1.4M files worth, and I'm selectively syncing that to my laptop. I would like for my system to act as if the data were actually local, and for sync to download data I or my programs are trying to access on demand. The problem, however, is that sync places an .rsls extension on all placeholder files. This is hugely annoying, and I don't see the need for it. Is there any way to configure selective sync to not add
  2. Hello, I had something strange happen sometime in the past 2 days. I have a number of folders sync'd across my laptop and 2 desktops. The problem I've noticed is in the syncing of my "Documents" folder, though I'm not sure if similar problems have occurred elsewhere. I just came back into the office for the first time since March. It had been a while since I logged into my desktops, and the sync'd Documents folders there may have been quite old. I didn't think that would be a problem. My laptop had the most current versions of files, as I had been working on it at home.
  3. Hi all, A bit of an edge-case perhaps. I would essentially like for all files to sync from RW to RO, but when an RW deletes, I don't want them deleted on the RO. I assume this isn't possible, but wanted to check in just in case. My use case is that I have torrent downloads synced from my home server (RW/owner) to my laptop (RO)... when I delete the torrent+data on RW, I still want them to remain on my RO laptop if I haven't moved them from the sync folder yet... thanks...
  4. So, updated to 2.2.2 on both machines, problem continues. Sync log on laptop (the originator of the share), shows something interesting - getting a VerifyFileSignature error. Perhaps this is the root of the problem? Any ideas how i might resolve? [2015-10-08 12:27:28] ACL[AA0E]: Failed to VerifyFileSignature - "blahblah - asdfsd\sadfasd - asdf\lsdkjfl.xxx" state: 1, fetime: 1433372237, time: 1433372237[2015-10-08 12:27:28] ACL[AA0E]: VerifyFileSignature: failed to find valid WriteACLEntry, user: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx[2015-10-08 12:27:28] MC[AA0E] [3
  5. Thanks, yeah, all of my shares work fine except for this one... Only issue with the office install is with some weirdness when BTSync keeps asking for admin login upon machine restart... fixed that once, but it's an issue again... doesn't seem to affect function as far as i can tell...
  6. Thanks for the reply, Moe. All are on 2.2.1. Will update to 2.2.3 as soon as I get the attention of my IT guy to get admin login and will report back...
  7. Hi folks, Been using BTSync for a good while now, and while most of my shares are syncing fine, I'm having issues with one of them. I use BTSync to sync files between my desktop and laptop, running BTSync 2.2.1 on Win 7 Enterprise x64. Looking at the log file, the peers are communicating, but something seems to happen when they start to try to send files between each other. I have tried deleting the share on the desktop and re-creating it, but the issue remains. The sync log on the desktop shows a repeating pattern. It processes get_nodes messages, and then decides that it "will send f