Bash script problems

Asked Aug 17 '18 at 10:44

Active Aug 17 '18 at 10:44

Viewed 31 times

This is my bash file script using Nexus Repository Manager API:

# Send Setup script
curl -u admin:admin123 -X POST --header 'Content-Type: application/json' \
http://localhost:8081/service/rest/v1/script \
-d @setup.json

# Test scripts
printf "---------------------- SCRIPTS ----------------------"
curl -u admin:admin123 -X GET http://localhost:8081/service/rest/v1/script

# Run script
curl -u admin:admin123 -X POST --header 'Content-Type: text/plain' \
 http://localhost:8081/service/rest/v1/script/setup/run

When I run it the input is:

curl: (3) Illegal characters found in URL
./setup.sh: line 3: http://localhost:8081/service/rest/v1/script: No such file or directory
./setup.sh: line 4: -d: command not found
./setup.sh: line 5: $'\r': command not found
./setup.sh: line 7: printf: --: invalid option
printf: usage: printf [-v var] format [arguments]
curl: (3) Illegal characters found in URL
./setup.sh: line 9: $'\r': command not found
curl: (3) Illegal characters found in URL
: No such file or directory/localhost:8081/service/rest/v1/script/setup/run
./setup.sh: line 13: $'\r': command not found

Where is the problem? Is it problem with backslashes?

asked Aug 17 '18 at 10:44

Wicia

2

What kind of line endings does the (script) file have? – Biffen Aug 17 '18 at 10:46
It is CR LF ... – Wicia Aug 17 '18 at 10:47
Then that’s the problem (except, perhaps, for the `printf` error). – Biffen Aug 17 '18 at 10:47
POSIX-based systems use `\n` as a line ending. the `\r` characters are confusing matters. That is, you're only escaping the `\r` character in the CRLF pair and then the line ends. – Phylogenesis Aug 17 '18 at 10:47
@Biffen so I should change CR LF -> LF? – Wicia Aug 17 '18 at 10:48
1

@Wicia Yes. E.g. with `dos2unix`. – Biffen Aug 17 '18 at 10:49

Bash script problems

0 Answers0