noahr

Thanks. This all pretty much worked. I went with the --config option. There is an anomaly I had to work through. On linuxA, I have four separate instances of rslsync running each sharing a single folder. On macB I have one instance, the Resilio Sync application connected to four shared folders. At first I tried to "Use predefined hosts" on macB. For each shared directory, specifying linuxA:port, where there are four different open ports, one for each instance. For whatever reason, this would allow only one active peer connection at a time. I had to kill 3 of 4 processes on linuxA to get the desired one to connect. Each of the four worked by itself. But not more than one at a time would connect. For the time being, I have switched to using Tracker Server, and all four work at once. Yay. I would just prefer to not use Tracker.

I have four directories on my linux system that I want to sync. For local security and management purposes, each folder (and all its contents) should have a different group owner and umask 0027. So, I thought I would initiate four parallel installs of rslsync. Each would be configured with just one of the folders shared. And rslsync would be launched with the desired group and umask settings four times. I've run into trouble because it seems the configuration for the second "instance" is clobbering the first. (which was initially working fine) I don't understand how to use these options appropriately. --config <path> Use a configuration file --storage <path> Storage path for identity and license Right now, without either specified, the second instance has interfered with the first. There is the .sync folder created in the shared folder. But there is also the .sync folder created... I guess under the working directory of the rslsync executable. Can anyone explain the stuff in the later folder, and how I might keep it all separated?