Description
Reported by @IVIJL
Also edit of .sh script through script-server has bug, when I saved it it was complaining that script is missing, but script was there updated from your server(did saved the changes) on same path with same rights but for server it was for some reason unreadable and server didnt see it even with same owner and rights as before. Must be some utf/EOL issue because only thing that helped is that I moved script away and created new file and just CTRL-V through nano there and server started to see it again.
when just editing and saving all went fine
but when CTRL-A copy to vscode in which I have LF line ending by default, then modify the script CTRL-A in vscode and put it back in server editor and hit save did make those CRLF endings
strange is that my vscode has LF ending by default so CRLF endings must have there been added through windows clipboard somehow
so just quick fix will be always apply LF line endings on save in server
as LF endings are not an issue in windows enviroments so will work fine everywhere but CRLF is problem in all linux enviroments.
also tested when I run simple sed -i 's/\r//' parameterized.sh it will fix line endings and runs again without problems.