kmindi

Members
  • Posts

    13
  • Joined

  • Last visited

kmindi's Achievements

Member

Member (2/3)

  1. That it is really unconvenient, please let me know of any progress, or if you need help with this feature.
  2. Hi, it seems that BitTorrent Sync can not handle a symbolic link that does point to another symbolic link which then points to a existing directory. I don't know what the specification of symlinks is on Windows, but it is working. (Just found that out by using `npm link` to symlink a node_module to a local folder where I have a modified version of the publicly available module). I have not tried a test case if this is the real cause of the hang of btsync (using 100% of cpu and only printing `sync manager not started` or similar lines in the debug enabled sync.log: [2015-08-19 00:45:57] MD[F28B]: Failed to apply folder changes [2015-08-19 00:45:57] MD[F28B]: Loading notifications [2015-08-19 00:45:57] MD[F28B]: [load notifications] Aborted: sync manager is not initialized and in the journal getting longer and longer growing lists of `processing file renaming` where the symlinced folder name and its parent are repeated over and over in a growing manner. Please make the symbolic link handling code aware of this ASAP (ready to test alpha builds on this). Or if the code is just following the link automatically and unaware of this behavior on windows, please make it aware of it. Check dir if it is a symlink and then check if linked folder is also a symlink and only sync the real target, some while loop should do the trick, possibly with a break condition after 100 links max (if thats not too high, cant think of a good reason of so many links following each other, other than the obvious circular dependency which should be avoided by the break)
  3. BitTorrent Sync should by default not sync well known temporary files that will get deleted right after the application that created them is closed or similar files. For a list of known temporary files please see http://www.file-extensions.org/filetype/extension/name/temporary-files. I have not reviewed all entries there but its only for extensions of files not for specific NAMEs of the file which also exists. I could not find a list of temporary file names (or regular expressions as these names usually consist of parts of the original file name). Maybe you could also start an inititive to standardizate this for the future ? Dropbox already ignores many of these temporary files per default....I would very much like to see it supported in this tool as well.