"-no-restart" is not fully documented about docs HOT 10 CLOSED

My guess is it can "never" be changed since there are scripts out there that depend on both.

from docs.

GUI wrappers which manage the syncthing process by itself instead of service-managers (systemd, launchd et al) should be able to control the startup of syncthing. As @calmh said we should not deprecate this, but I agree to @lkwg82 we should keep and document it.

from docs.

The option historically takes its name from the fact that when set syncthing does not restart when told to restart, nor when it crashes, it just exits. As an effect of suppressing the monitor process. It is the equivalent of the STNORESTART environment variable. We have both for ... you guessed it, historical reasons. :)

from docs.

see also #94

from docs.

So is this historical reason still valid or is this just an usefull opportunity to remove some historical waste? ;)

from docs.

bump

from docs.

What are these scripts? What for? Can we give some warning over a long time "deprecated switch, instead use this ..."?

from docs.

Probably all over the place. I don't see much value in deprecating it, it's literally half a line of code to support the env var in addition to the command line switch.

from docs.

So we should keep and document it.

from docs.

Fixed by #278

from docs.