Its the output from running command rclone config show, but with passwords, tokens and other sensitive information removed.
Correct. With -vv it will just print more information to the command window where you run the mount command. If you rather want the output to a file, also use something like --log-file=logfile.txt (see: Documentation)
I think it is a limitation when working with certain backends: Those that do not support directly updating ModTime. Koofr is such a backend, also Jottacloud which I tested with. Normal rclone copy/rclone sync will work around this by re-uploading the file, but not the mount. I'm not sure if it is a bug or a limitation, or something in between... I've created an issue for it on github, so hopefully someone will enlighten us either here or there...
The problem, from a user's perspective, is that SetModTime support is not directly documented. Also some commands, like copy and sync, will re-upload automatically if backend does not support SetModTime, so it's easy to miss. (We have issue 1066 for improving documentation on this).
Seems one can use rclone touch on an existing file to check the support:
rclone.exe touch remote:/existing_file.txt
2021/09/26 19:20:02 ERROR : Attempt 1/3 failed with 1 errors and: touch: couldn't set mod time: can't set modified time
2021/09/26 19:20:02 ERROR : Attempt 2/3 failed with 1 errors and: touch: couldn't set mod time: can't set modified time
2021/09/26 19:20:02 ERROR : Attempt 3/3 failed with 1 errors and: touch: couldn't set mod time: can't set modified time
2021/09/26 19:20:02 Failed to touch: touch: couldn't set mod time: can't set modified time
It is an option?
I understand from Koofr Document, that it uses the Koofr API.
So I don't really understand how possible the edit it from rclone "implement it in rclone."?
If it is possible It be Great! ^^