![]() However, this issue was fixed when updating all the systems to v1.17.0 which included some improvements to the encrypted folders, making all my systems to be perfectly in sync! Bear also in mind that the provided version by the operating system, like the one in Raspbian is really old, and was causing issues with encrypted folders with the systems in fedora… once all of them were updated, it worked fine (there were messages about encrypted folder being announced but not configured when the Raspbian version was 1.0.0). One easing feature here is that one host can be configured as presenter which allows other systems to inherit the know list of hosts from the host marked as presenter, making it easier to do the both-ways initial introduction.īest outcome, is that the use (or abuse) of RAM has been completely slashed what rslsync was using.Ĭurrently, the only issue is that for some computers in the local network the sync was a bit slow (it even got some remote underpowered devices syncing faster than local ones), but some of the copies were fully in synced already. One difference is that in rslsync having the secret for the key is enough, in syncthing you need to add the hosts in both ways to accept them and be able to share data. Once done, we’re ready to start adding folders and systems. It is recommended to define a GUI username and password for avoiding other users with access to the system from altering the configuration.Once the process is started, the browser can be pointed locally at to start configuration: Only caveat, if using Debian, is to use the repository they provide as the package included in the distribution is really old, causing some issues with the remote encrypted peers.įor starting as user the command is very simple: In addition, it includes systemd support and it’s packaged in the operating system, making it really easy to install and update (´rslsync´ was without updates for almost a year). Syncthing is now is covering some of the features I was using with rslsync: I finally decide to give syncthing another try after years since last evaluation. After checking with their support (as I had a family license), the workaround was to remove the folder and create a new one, which in parallel meant having to configure it again on all the systems that used for keeping a copy. The problem is that even one file is deleted long ago, rslsync does keep it in the database… and in memory. My NAS with 16 GB of ram, even if a bit older (HP N54L), seemed not to have enough memory to run it, and was constantly swapping.Ĭhecking the list of processes pointed to the rslsync process as the culprit, and apparently the cause is the way it handles the files it controls. Some years ago I started using geo replication to keep a copy of all the pictures, docs, etcĪfter being using BitTorrent sync and later resilio sync (even if I didn’t fully liked the idea of it being not open source), I gave up.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |