• Content Count

  • Joined

  • Last visited

About luckman212

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I had that same thought too TJ 🙂 Somehow I doubt it though. That would almost be too clever. Hope someone from the mother ship can give us an official answer though.
  2. It appears that lines beginning with "#" would be skipped when parsing the IgnoreList, since at the top we have lines like # IgnoreList is a UTF-8 encoded .txt file that helps you specify single files, paths and rules # for ignoring during the synchronization job. It supports "?" and "*" wildcard symbols. But, in the default IgnoreList for new folders, these 3 lines also exist (seems related to Synology Drive app): #recycle #snapshot #SynoRecycle I am assuming that this is either a mistake, or somehow this isn't working because I guess these lines would be "ignored by the IgnoreL
  3. a little more... After reading this page again, it seems like maybe there is an API but it is quite hidden and difficult to enable(?). Looks like possibly if the `api_key` value is configured in sync.conf then the API might be enabled. But, there is no sync.conf anymore, just bencoded settings.dat which is protected with salted hash. At this page, there is a link to Python2 script which can decode the encrypted settings.dat file—but how can this be turned back into a valid settings.dat? Reading this page it looks like it may be possible to run Sync in conf
  4. Coming back 1 year later to this idea 🙂 Today I again found that one of my folders was no longer syncing - it had a red Exclamation (!) mark and said Database error (link to KB article: I had to Disconnect, manually sync the folders on all peers using rsync, and then re-connect to clear this up. RslSync version was 2.7.1 on all peers. Apparently the sync had been broken for >1 week and I was not aware of it. Some sort of API / alerts / commandline method to query status would have really helped here! Is there any chance this could be
  5. This is great news, and a very nice surprise! Thank you all so much Stay healthy & safe
  6. Can you please post the solution publicly? It would benefit others...........
  7. Now Resilio Connect is at v2.8 -- hope Sync Pro gets a new desktop build soon... still at 2.6.x 😞
  8. Will there be a new release of Sync soon? It's been awhile. Is this still the latest beta version?
  9. I would buy some Resilio swag too!
  10. Pretty quiet around here...too quiet
  11. What type of system(s) are these? Linux, macOS, Windows? Should be pretty easy to periodically run a script that compares the hash of a file to a previously known value and does something when it changes. If your system is Linux you can run the script every minute with cron etc. Here's a bash script I slapped together... you'll need the sha256sum binary, which you can get for just about any platform. See GNU coreutils or if you're on macOS and have Homebrew, `brew install coreutils`. This won't work for Windows but something similar can be done in PowerShell if needed. #!/usr/bin
  12. I noticed today just by accident that one of my folders was stuck at 100% - sync was not completing for some reason. I had to enable debug mode and found a file that had a weird resource fork for whatever reason was causing the sync to hang. I deleted that file, restarted Sync on both ends and it was green again. So the question is: I would like to know if there is any way to get the sync status via command line / Terminal / bash? I would make a periodic script (cron, LaunchAgent on mac etc) to run and if the sync is not complete then maybe pop a notification, send an alert to Pushover e
  13. Hey guys I saw Rsl Connect is up to 2.7.x now. So I assume core sync engine is up to 2.7, which is also used by Rsl Sync Home /Pro. Is there going to be an updated client release soon? Thx