Shell Programming and Scripting

There is a typing error in the first line:

The space after the # will cause the change of shell to be ignored.
Try.

Code:

#!/bin/bash

There is a space in your shebang line.

Perfect. That fixed it. I was always manually running the script in bash, thats why I was not getting the error. Removed the space and it works like a charm.

Thanks All. For quickly resolving this.

One more quick question.

In the Logs when I echo PROGRESS. The value is as below.

?Invalid command ?Invalid command ?Invalid command ?Invalid command ?Invalid command ?Invalid command ?Invalid command ?Invalid command ?Invalid command ?Invalid command ?Invalid command ?Invalid command ?Invalid command
?Invalid command ?Invalid command ?Invalid command ?Invalid command ?Invalid command ?Invalid command ?Invalid command ?Invalid command ?Invalid command ?Invalid command ?Invalid command ?Invalid command ?Invalid command ?Invalid command ?Invalid command ?Invalid command
Connected to XX.XX.XX.XX(vsFTPd 2.0.3) 331 Please specify the password. 230 Login successful. 200 PORT command successful. Consider using PASV. 150 Ok to send data. 226 File receive OK. local: File.txt remote: File.txt 14352 bytes sent in 0.086 seconds (162.20 Kbytes/s) 221 Goodbye.

Why is it showing ?Invalid command. The FTP is working fine. But Logs are not good.

There is a major logic error in the script in this area:

Earlier in the script many text lines are appended to $PROS_LOAD_LOG and then a few ftp commands are appended on the end of this file. The whole content of the file ${PROS_LOAD_LOG} is then given to ftp to process - hence the error messages! You need to separate the ftp input commands from the output log.

I thoguht I could use the same file. I changed it to a new file and it works fine. Thanks methyl for resolving that. This is a Great Forum.

Your'e welcome