Zone

Members
  • Posts

    9
  • Joined

  • Last visited

Everything posted by Zone

  1. were are these files "7. delete *.db, *.db-shm, *.db-wal" stored?
  2. I'm still experiencing this issue and now not receiving notifications to approve new clients with 1.4.92
  3. In my experience using BitTorrent Sync across 10 read-only peers has continuity issues. I use BitTorrent sync to sync files and setting for a program. The first Sync complete without issues. Unfortunately after that BitTorrent Sync tends to leave dirty files. For instance I delete a file or change a file that is not always appropriately Synced if the client is off line or a program is utilizing synced files. First case when the client is off line and changes are made to the files, when the client comes online these changes are often not carried over. Leaving outdated or deleted files on the peer client. Causing the program to crash as it needs specific versions of these files with their proper configuration. I even had issues with this when a client is online and changes are made. The second case is when those client files in my case are used by a program. Because the program accesses BitTorrent Sync considers these files modified and therefore out of sync. Despite having the clients check the box "overwrite modified files"files do not get consistently overwritten. When the program is not running BitTorrent Sync should overwrite the modified files. In summary my clients are not receiving synced data, retaining old data and not overriding modified file with original or updated versions. Any suggestions? Is there a way I can force my clients to remove all files in the folder and re-sync? I've tried removing all the files from the host hoping that the clients refresh. Unfortunately in most cases BitTorrent Sync fails to delete or overwrite files.
  4. To me that an extremely important feature! I often work with many computers where I need files. Due to the nature of my work it's not productive or in some cases not possible to install the program on a host machine. Please make this portable and runnable without elevated privileges.
  5. So I have 10 peers that are read-only. Is this done from my client (the source of files) or on their client (the receiver of the read-only files) or is this during the "sharing" the key when you select read-only? Either way I do not see an option during "sharing" the read-only key or the option of applying it to the 10 read-only clients from my client.
  6. I have 10 peers how do I check the "overwrite" preference? When I right click, folder in bit torrent sync then click preferences I do not see an option for "Overwrite".
  7. I use torrent sync to distribute mods to update minecraft clients for the server through BitTorrent Sync read-only. The goal was to create a system that was seamlessly update my communities minecraft clients by altering the files on my computer and syncing the changes to there's. The initial sync works as expected. All nine of my clients are minecraft up-to-date. I've two folders that are synced "mod" and "config" folder that are distributed to minecraft. When any of the minecraft clients executes the BitTorrent sees the "mod" and "config" folder as out of date. When I examine what BitTorrent Sync claims to be out of sync the files are identical. This causes trouble when I update minecraft mod files. I remove the "mod" file files then replace them with up-to-date versions which have different names. Then add new or add altered "config" files which generally have the same file names. Bit torrent sync does not remove update all the files. The folder structure looks like this. "mod" folder mod 1 mod 2 mod 3 ... "config" folder Config 1 Config 2 Config 3 ... If I change files or config files within the folders some files are not removed. If I temporarily remove both the mod and config folders and then add them back everything sync correctly. Unfortunately that requires intervention on my part and for the client BitTorrent to be online. Explaining this really isn't easy and if you need clarification don't hesitate to ask.