• Posts

  • Joined

  • Last visited

Everything posted by sbhouchen

  1. Is this also true for CentOS 6.9? My server with kernel 2.6.32-696.30.1.el6.x86_64 isn't getting filesystem notifications. The filesystem type is ext4. I'm running Sync 2.5.13, installed via yum.
  2. Error when doing 'yum update' on CentOS 6, updating from 2.5.10: (13/13): resilio-sync-2.5.12-1.x86_64.rpm | 11 MB 00:01 ------------------------------------------------------------------------------------------------------------------------------------------------- Total 8.2 MB/s | 103 MB 00:12 warning: rpmts_HdrFromFdno: Header V4 RSA/SHA256 Signature, key ID 3f171de2: NOKEY Public key for resilio-sync-2.5.12-1.x86_64.rpm is not installed
  3. The change log in that screen shot matches the content of the 2.5.8 change log.
  4. There's nothing in the change log about 2.5.9
  5. I disagree that it has been addressed (satisfactorily). Every new user doesn't know to read those three articles. But, by default, Sync eats their HDD or SSD for lunch. I followed the instructions in those posts long ago, and the logging no longer happens on my computers. Having a default behavior that does excessive and needless logging, and requiring users to search a forum for a solution that requires editing the registry and manually unregistering DLLs doesn't really address the problem. Perhaps disable the logging by default, with an option to turn it on in the case that support needs to see logs from a specific user?
  6. The issue with ShellExtIO.log has been discussed here for a very long time, and needs to be taken seriously by the developers. We've been dealing with this for too long. Please disable the logging completely or give the end user an option to turn it off. It is totally needless.
  7. I don't know what's going on with the CAM tool, but the difference between Resilio Sync's number and the one in Task Manager is the difference between MegaBITS and MegaBYTES per second.
  8. I have 2.5.x on all desktops and my iPad running 2.4.x works just fine.
  9. Helen, do you know how soon the "try again later" happens?
  10. @RomanZ Please confirm that you received the logs and screen shots of Resource Monitor on support request #45987. Thanks!
  11. @Skeptic, did you modify the config file to allow the web ui to be available from other hosts (with method 1)?
  12. Lightroom catalog folders contain many "preview" files, so I understand that there's a lot for Sync to do. I have 64,781 files in 64,092 folders, consuming 47.5 GB. All of this is on an internal SSD. Maybe it simply takes a long time to do the job. My memory might be incorrect, but I think the indexing task used to be less resource intensive. However, bugs have been fixed since then and it is possible that doing it the "right way" takes more resources.
  13. I'm running 2.3.7 on Windows 10, and my Lightroom catalog folder seems to be constantly indexing. It was even worse with 2.3.8. @KawateTadako were you able to upload any of your logs for analysis?
  14. @RomanZ I just submitted logs on support request #45987. Nothing special about this setup... C: drive is an internal SSD.
  15. I'm also noticing very heavy disk and CPU usage on Windows 10 by 2.3.8. I can confirm that everything looks "normal" after reverting to 2.3.7.
  16. It is the sync_trash_ttl setting described here:
  17. I see that this version is available via auto-update.
  18. I think the original poster was thinking that because the identical files would (probably) have the same hash, Sync might be smart enough to send the data across the network once, but put the file in all 10 locations. This is sort of similar to how Sync keeps hashes for files in the archive and will not resend data over the network if a matching file is found in the archive.
  19. In the future, could this log be disabled or at least configurable via advanced settings?
  20. To me, it doesn't seem useful to create this log file. IF nobody else has access to it, and hopefully that is truly the case, then there's no point to creating the log file in the first place. Remember, the original poster found the file when trying to find out where disk space was going. If it isn't necessary to create this log file, please configure a future release of Sync such that no logging takes place.
  21. In the preferences for that folder, do you have "Overwrite any changed files" turned on?