rclone is trying to add shell_type = unix so why not just add it yourself.
then rclone will not modify the config file.
and when rclone runs the first command on nas_photos_manager:, rclone will often add something like
Oh I am sorry. I must admit that I did not search the forum but the issue tracker and did not find a suitable one. Maybe I was not thoroughly enough. Spent a hard day on switching the backend from FTP to SFTP as you saw in other posts
Thanky anyway also for the additional parameters I better add beforehand...
sure, when using a token based remote, such as gdrive, when the token expires, rclone has to re-write the config file.
another option, something i do alot, is not to use a config file at all.
instead create an on-the-fly remote. rclone copy :sftp,host=example.com:path/to/dir /tmp/dir
Hm. Sounds interesting. But I guess this is not the best solution for my usecase (at least from what I think that I know right now :-D)
I use RClone to mount storage sitting on a NAS from within a hypervisor and then pass-through it to containers. Therefore I use the fstab mount way on the hypervisor to have a reliableconnection to the backend when it is needed (like with the noauto mount option).
But I might be mistaken and your solution is appropriate as well. I will have a look.