Port change is not reflected in usage of Syncthing (manual restart is needed)
ineiti opened this issue · 5 comments
On my mac I have two syncthing instances, one for each user. So I changed the port of one of the instances in order for them to run in parallel. Now the following happens for the syncthing with the changed port:
- it seems to me that the status icon follows the syncthing of the other user with the default port
- when I click on the icon and choose
Open, it opens the syncthing with the default port. Same thing if I click the icon, choosePreferencesand thenOpen Syncthing in Browser
you need to click on the icon -> Preferences -> enter the URI -> click test. Then close syncthing and restart it. Then the non default port should be used. Keep in mind you should also set the API key based on the instance.
OK, seems I didn't quit and start Syncthing again.
Reopened because we should at least document this behaviour. And probably we should fix it so it is live changed and it doesn't need restarted. For my own administration: this behaviour is probably due to the default functionality and syncthing daemon background process are not synced when updating. Then the background process should be stopped/killed and then started again after the change and given the new setting.
There might be other configuration changes that need to be reloaded, no? So perhaps for every configuration change, do this reloading of the daemon.
Exactly, like the environment variables and the hidden commandline arguments.