Screenshot for nssm service manager doesn't match option description · Issue #920 · syncthing/docs · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Path to your syncthing.exe and enter --no-restart --no-browser --home="<path to your Syncthing folder>" as Arguments.
but screenshot of nssm service manager show: -no-console -no-browser -home="C:\Syncthing"
I ran syncthing serve --help and it looks like option --no-console doesn't exist anymore.
Also, I suggest:
to advice to install syncthing into C:\Program Files instead of C:\Syncthing because by default all users of workstation might have write access into C:\Syncthing.
since syncthing supposed to run as the SYSTEM account (to be able to sync multiple user's accounts, as well system folders), it would be more secure to use SYSTEM's home directory to prevent unauthorized user(s) to read/write to syncthing data/configuration files, that's why suggestion to use:
it looks like option --no-console doesn't exist anymore.
--no-console does still exist (see https://docs.syncthing.net/users/syncthing for all available command line options). However, it is true that the screenshot is outdated, and what is more important, the upcoming Syncthing v2 requires double -- in command line arguments, so if you are setting up Syncthing now, the safe way is to use only -- instead of the older, single - version.
I'm sorry for confusion, I ran syncthing serve --help on Linux and expected to see Windows's only option --no-console. It is there as it should be, on Windows version.
Text stated:
but screenshot of
nssm
service manager show:-no-console -no-browser -home="C:\Syncthing"
I ran
syncthing serve --help
and it looks like option--no-console
doesn't exist anymore.Also, I suggest:
syncthing
intoC:\Program Files
instead ofC:\Syncthing
because by default all users of workstation might have write access intoC:\Syncthing
.syncthing
supposed to run as theSYSTEM
account (to be able to sync multiple user's accounts, as well system folders), it would be more secure to useSYSTEM
's home directory to prevent unauthorized user(s) to read/write tosyncthing
data/configuration files, that's why suggestion to use:The text was updated successfully, but these errors were encountered: