Not all platforms react in the same way to CLI commands.
While e.g. in Windows, among other things, the CLI parameter -reset-deltas reacts as expected, the process reacts only to a limited extent in other environments. If this e.g. run on a Synology in this way as
Although the process starts, it does not work as required, even if the syncthing process is stopped. Such differences also lead to uncertainty when the processes show up differently.
The feature request would be that all CLI functions are integrated into the GUI so that their correct and efficiently usable functionality is given. This would also simplify the support.
Sounds like a good idea. Maybe Syncthing’s monitor process can do the --reset-deltas by exit code? Or let’s just have an exit code where wrappers can do the --reset-deltas restart accordingly if they see it.
I have to do the same extra work every time a delta reset is required on my QNAP devices. This is SCPing in, going to a deep QPKG subdir and editing the wrapper shell script plus later returning to change it back to the original version.
Probably because it runs with a different user and home directory when run by the actual start script, so what he does on the command line as another user has no effect.
I can then observe that the GUI reactivates and the processes work differently than in normal operation. The CMD also cooperates in a traceable manner in parallel.
If I do the same with a Synology, there is no interaction. There are also no noticeable changes, as is the case with Windows when there is an error.
Well, if there’s a start-up script running Syncthing as a special user, you’ll need to run as that user, too. At least it sounds like it isn’t doing user namespacing…
